ads.id ▶ Indonesia Internet Publishing, Advertising and Marketing Community

Ads.id | Key Trends

Online Status

Online

Server IP address resolved: Yes
Http response code: 200
Response time: 1.93 sec.
Last Checked: 02/03/2025

Ads.id attracts 5,499 unique visitors daily, generating 9,568 pageviews. The estimated value of ads.id is 168,718 USD. Each visitor views approximately 1.86 pages on average.

According to Majestic's traffic estimates, ads.id ranks 467,672 globally, with the majority of its visitors coming from Indonesia, where it holds the 1,241 position.

See the list of other websites hosted by CLOUDFLARENET - Cloudflare, Inc., US.

Ads.id is registered with the .ID top-level domain. Explore additional websites within the .ID zone.

A recent examination on (October 12, 2024), indicates that ads.id has an expired SSL certificate issued by Google Trust Services (expired on November 26, 2024). Click the "Refresh" button in the Safety Information section for updated SSL details. See the list of websites using SSL certificates issued by Google Trust Services.

According to Google Safe Browsing, Google Safe Search and Symantec ads.id appears to be a safe domain.

Based on Google's Mobile-Friendly test, ads.id is optimized for mobile and tablet devices, although the web page loading speed could be improved.

Ads.id | General Site Information

Global Rank

76,576

Average Load Time

1.51sec

Links In Count

494

Website Value

$157,680

Audience Geography. Where are ads.id visitors located?

Country	Visitors
Indonesia ID	89.2%
Cambodia KH	2.3%
Singapore SG	1.8%
India IN	0.7%
Other	6.1%

Country	Pageviews
Indonesia ID	90.3%
Cambodia KH	1.4%
Singapore SG	1.1%
India IN	0.4%
Other	6.7%

Country	Rank
Indonesia ID	1241
Cambodia KH	2219
Singapore SG	24444
India IN	332699

Where do visitors go on ads.id?

Subdomain	Pageviews
ads.id	99.56%
verifikasi.ads.id	0.44%

Subdomain	Pageviews per User
ads.id	1.7
verifikasi.ads.id	1

Subdomain	Reach
ads.id	100%
verifikasi.ads.id	0.77%

How popular is ads.id?

Period	Global Rank	Global Rank Delta
past 3 months	76576	-23597
past month	82923	10478
past week	73886	-29022
yesterday	87645	-5610

Days	Pageviews Rank	Pageviews Rank Delta	Pageviews per Million	Pageviews per Million Delta	Pageviews per User	Pageviews per User Delta
90	108214	-29612	49	38%	1.74	1%
30	116643	13850	45	-15.66%	1.8	-1.13%
7	101229	-44901	56	56%	1.9	10%
1	112928	-30420	5	20%	2	30%

Days	Reach Rank	Reach Rank Delta	Reach per Million	Reach per Million Delta
90	68542	-21343	105	36%
30	74347	9244	95	-14.71%
7	68742	-25107	10	40%
1	80735	3555	87	-7.768%

Ads.id | Safety and Security Details

Overview

Last Updated: 02/03/2025

Overall result - ads.id is safe.

We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.

Norton Connect Safe

Last Updated: 03/21/2024

ads.id is safe.

Norton ConnectSafe evaluates ads.id for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search

Last Updated: 02/06/2019

ads.id is safe.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing

Last Updated: 01/09/2019

ads.id is safe.
Malware: not found.
Phishing: not detected.
Unwanted software: not found.
Harmfull applications: not found.

Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.

Site Advisor

Last Updated: 02/22/2021

ads.id is safe.

McAfee assesses ads.id for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze ads.id for mature or inappropriate content, only security checks are evaluated.

Web of Trust

Last Updated: 02/03/2025

ads.id child safety is unknown.

The WOT calculates reputation of the ads.id. This reputation system receives ratings from users and information from third-party sources, assesses the ads.id for safety features and confirms, whether ads.id is suitable for children.

Ads.id | SSL Certificate Information

SSL Checker Tool

Domain	ads.id
Issuer Organization	Google Trust Services
Issuer	WE1
Algorithm	ecdsa-with-SHA256
Valid form	08/28/2024
Expiration	11/26/2024
Signed	Certificate is not self signed
Additional Domains	ads.id *.ads.id

Ads.id | Server and Hosting Details

Server Location

Geolocation Tool

Ads.id ASN Information

ASN Lookup Tool

ASN ID: 13335
ASN Title: CLOUDFLARENET - Cloudflare, Inc., US

Last Update: 07/15/2024

ASN Whois

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 13335
ASName: CLOUDFLARENET
ASHandle: AS13335
RegDate: 2010-07-14
Updated: 2017-02-17
Comment: All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse
Ref: https://rdap.arin.net/registry/autnum/13335

OrgName: Cloudflare, Inc.
OrgId: CLOUD14
Address: 101 Townsend Street
City: San Francisco
StateProv: CA
PostalCode: 94107
Country: US
RegDate: 2010-07-09
Updated: 2017-02-17
Comment: All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse
Ref: https://rdap.arin.net/registry/entity/CLOUD14

OrgTechHandle: ADMIN2521-ARIN
OrgTechName: Admin
OrgTechPhone: +1-650-319-8930
OrgTechEmail: rir@cloudflare.com
OrgTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN

OrgAbuseHandle: ABUSE2916-ARIN
OrgAbuseName: Abuse
OrgAbusePhone: +1-650-319-8930
OrgAbuseEmail: abuse@cloudflare.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN

OrgNOCHandle: NOC11962-ARIN
OrgNOCName: NOC
OrgNOCPhone: +1-650-319-8930
OrgNOCEmail: noc@cloudflare.com
OrgNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN

RNOCHandle: NOC11962-ARIN
RNOCName: NOC
RNOCPhone: +1-650-319-8930
RNOCEmail: noc@cloudflare.com
RNOCRef: https://rdap.arin.net/registry/entity/NOC11962-ARIN

RTechHandle: ADMIN2521-ARIN
RTechName: Admin
RTechPhone: +1-650-319-8930
RTechEmail: rir@cloudflare.com
RTechRef: https://rdap.arin.net/registry/entity/ADMIN2521-ARIN

RAbuseHandle: ABUSE2916-ARIN
RAbuseName: Abuse
RAbusePhone: +1-650-319-8930
RAbuseEmail: abuse@cloudflare.com
RAbuseRef: https://rdap.arin.net/registry/entity/ABUSE2916-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

Ads.id | Domain Name Information

WHOIS

WHOIS Lookup Tool

Domain Whois

ID ccTLD whois server
Please see 'whois -h whois.id help' for usage.

Domain ID: PANDI-DO291136
Domain Name: ads.id
Created On: 2014-06-13 09:17:28
Last Updated On: 2024-08-28 07:06:15
Expiration Date: 2025-06-13 23:59:59
Status: clientTransferProhibited
Status: serverTransferProhibited

====================================================
Sponsoring Registrar Organization: PT Digital Registra Indonesia
Sponsoring Registrar URL: www.digitalregistra.co.id
Sponsoring Registrar Street: Jl. lempongsari no. 39C Jongkang RT/RW 12/35 Sariharjo
Sponsoring Registrar City: Sleman
Sponsoring Registrar State/Province: Yogyakarta
Sponsoring Registrar Postal Code: 55281
Sponsoring Registrar Country: ID
Sponsoring Registrar Phone: 0274882257
Sponsoring Registrar Email: info@digitalregistra.co.id
Name Server: ivan.ns.cloudflare.com
Name Server: uma.ns.cloudflare.com
DNSSEC: Unsigned

Abuse Domain Report https://pandi.id/domain-abuse-form/?lang=en
For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en

DNS Records

DNS Lookup Tool

Host	A Record	TTL

Host	MX Record	Priority	TTL

Host	NS Record	TTL

Host	TXT Record	TTL

Ads.id | HTML Validation Report

HTML Validation Tool

Errors

Element “span” is missing one or more of the following attributes: “role”.

Bad value “Mon, 04 Dec 2017 14:10:28 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 30 Nov 2017 13:25:08 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 26 Nov 2017 12:25:51 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 24 Nov 2017 14:10:53 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 17 Nov 2017 05:55:22 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 14 Nov 2017 01:56:05 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 13 Nov 2017 05:10:38 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 31 Oct 2017 23:10:55 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 25 Oct 2017 09:25:58 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 12 Oct 2017 14:10:12 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 22 Sep 2017 16:10:26 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 02:58:30 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 01:12:15 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 09:17:14 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 30 Nov 2017 02:52:10 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 15:46:14 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 12:27:12 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 07:40:47 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 02:54:11 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 14:54:13 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 12:55:48 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 05:37:35 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 13:53:03 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 12:05:19 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 11:04:07 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 15:39:39 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 28 Nov 2017 12:07:43 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 28 Nov 2017 11:26:20 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 19:17:46 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 18:33:49 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 08:19:04 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 04:04:15 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 15:53:54 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 15:49:41 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 14:49:22 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 13:54:28 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 23:36:12 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 08:22:39 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 04:32:23 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 15:37:27 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Wed, 29 Nov 2017 14:38:28 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 26 Nov 2017 07:34:09 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 26 Nov 2017 03:21:04 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 12:27:29 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 03:19:40 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 12:38:27 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 09:12:44 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 02:58:45 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 04:28:28 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 12:03:39 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 06:56:14 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 12:39:06 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 17:48:25 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 12:20:05 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 07:27:31 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 04:01:30 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 01:09:12 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 15:21:12 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 03:55:39 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 30 Nov 2017 12:32:43 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 28 Nov 2017 17:52:40 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 17:17:43 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 12:38:50 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 12:13:11 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 10:11:49 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 15:55:29 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 10:47:54 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 09:57:35 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 03:10:23 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Mon, 04 Dec 2017 02:28:38 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 10:14:53 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 09:38:52 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 04:53:27 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Tue, 05 Dec 2017 11:44:31 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sun, 03 Dec 2017 21:18:33 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 11:12:09 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 07:01:05 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Sat, 02 Dec 2017 05:24:28 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 14:01:57 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Fri, 01 Dec 2017 08:19:50 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 30 Nov 2017 01:05:30 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

Bad value “Thu, 30 Nov 2017 00:51:49 +0000” for attribute “datetime” on element “time”: The literal did not satisfy the time-datetime format.

The “itemprop” attribute was specified, but the element is not a property of any item.

Warnings

Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.

Ads.id | Desktop Performance Insights

Last tested: 06/13/2016

Desktop

Desktop Speed

79%

Leverage browser caching

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Reduce server response time

Optimize images

Minify HTML

Desktop Resource Breakdown

Total Resources	49
Number of Hosts	10
Static Resources	40
JavaScript Resources	15
CSS Resources	5

Ads.id | Mobile Performance Insights

Last tested: 12/02/2019

Mobile

Mobile Usability

98%

Size tap targets appropriately

Mobile Speed

39%

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Avoid landing page redirects

Leverage browser caching

Optimize images

Prioritize visible content

Reduce server response time

Minify CSS

Mobile Resource Breakdown

Total Resources	121
Number of Hosts	26
Static Resources	73
JavaScript Resources	36
CSS Resources	9

Ads.id | Common Typographical Errors

www.ads.com
www.ads.net
www.ads.org
www.ads.info
www.ads.biz
www.ads.us
www.ads.mobi
www.ds.id
www.ads.id
www.qds.id
www.aqds.id
www.qads.id
www.wds.id
www.awds.id
www.wads.id
www.sds.id
www.asds.id
www.sads.id
www.zds.id
www.azds.id
www.zads.id
www.as.id
www.axs.id
www.adxs.id
www.axds.id
www.ass.id
www.adss.id
www.aes.id
www.ades.id
www.aeds.id
www.ars.id
www.adrs.id
www.ards.id
www.afs.id
www.adfs.id
www.afds.id
www.acs.id
www.adcs.id
www.acds.id
www.ad.id
www.adw.id
www.adsw.id
www.adws.id
www.ade.id
www.adse.id
www.add.id
www.adsd.id
www.adds.id
www.adz.id
www.adsz.id
www.adzs.id
www.adx.id
www.adsx.id
www.ada.id
www.adsa.id
www.adas.id

Ads.id Indonesia Internet Publishing, Advertising and Marketing Community

Tempat berkumpulnya netpreneur Indonesia.

Ads.id | Key Trends

Ads.id | General Site Information

Ads.id | Safety and Security Details

Ads.id | Server and Hosting Details

Ads.id | Domain Name Information

Ads.id | HTML Validation Report

Ads.id | Desktop Performance Insights

Ads.id | Mobile Performance Insights

Ads.id | Competitors Analysis

Ads.id | Common Typographical Errors