ap7am.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
80
ap7am.com was registered on 5 Jun 2008 via Name.com, Inc. and the registry expiry is 5 Jun 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/ap7am.com.
ap7am.com publishes 2 nameservers. DNSSEC is not signed.
ap7am.com has 4 IPv4 addresses (3.167.227.109, 3.167.227.117, 3.167.227.37, 3.167.227.58) and 8 IPv6 addresses (2600:9000:27e6:4e00:17:873f:7140:93a1, 2600:9000:27e6:5200:17:873f:7140:93a1, 2600:9000:27e6:6000:17:873f:7140:93a1, 2600:9000:27e6:7400:17:873f:7140:93a1, 2600:9000:27e6:b000:17:873f:7140:93a1, 2600:9000:27e6:c00:17:873f:7140:93a1, 2600:9000:27e6:ce00:17:873f:7140:93a1, 2600:9000:27e6:f600:17:873f:7140:93a1). The geolocation database places 3.167.227.109 in Frankfurt am Main, Germany.
The TLS certificate from Amazon RSA 2048 M04 is valid and has 51 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Amazon CloudFront, Amazon Web Services, HSTS, HTTP/3 and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for ap7am.com in the checks that ran.
ap7am.com was registered on 5 Jun 2008 via Name.com, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/ap7am.com.
| Registered | since 5 Jun 2008 |
|---|---|
| Created | 5 June 2008 |
| Updated | 28 February 2026 |
| Expires | 5 June 2028 |
| Registrar | Name.com, Inc. |
| Status | client transfer prohibited |
| Nameservers | norm.ns.cloudflare.com, sara.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/ap7am.com |
ap7am.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver norm.ns.cloudflare.com is published for ap7am.com in the registration record from https://rdap.verisign.com/com/v1/domain/ap7am.com.
Nameserver sara.ns.cloudflare.com is published for ap7am.com in the registration record from https://rdap.verisign.com/com/v1/domain/ap7am.com.
ap7am.com has 12 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 3.167.227.109, 3.167.227.117, 3.167.227.37, 3.167.227.58 |
|---|---|
| AAAA | 2600:9000:27e6:4e00:17:873f:7140:93a1, 2600:9000:27e6:5200:17:873f:7140:93a1, 2600:9000:27e6:6000:17:873f:7140:93a1, 2600:9000:27e6:7400:17:873f:7140:93a1, 2600:9000:27e6:b000:17:873f:7140:93a1, 2600:9000:27e6:c00:17:873f:7140:93a1, 2600:9000:27e6:ce00:17:873f:7140:93a1, 2600:9000:27e6:f600:17:873f:7140:93a1 |
| NS | norm.ns.cloudflare.com, sara.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.ap7am.com is "v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected];".
IPv4 address 3.167.227.109 answers for ap7am.com at resolver 1.1.1.1:53.
IPv4 address 3.167.227.117 answers for ap7am.com at resolver 1.1.1.1:53.
IPv4 address 3.167.227.37 answers for ap7am.com at resolver 1.1.1.1:53.
IPv4 address 3.167.227.58 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:4e00:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:5200:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:6000:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:7400:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:b000:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:c00:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:ce00:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
IPv6 address 2600:9000:27e6:f600:17:873f:7140:93a1 answers for ap7am.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
ap7am.com is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 3.167.227.109 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
The certificate for ap7am.com is valid, with 51 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M04 |
|---|---|
| Subject | *.ap7am.com |
| Valid from | 7 June 2026 |
| Valid until | 21 December 2026 |
| Days left | 51 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.ap7am.com, ap7am.com.
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Nginx is filed under Web servers, Reverse proxies.
The homepage returned HTTP 200 in 6 ms. The target title is 61 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 6 ms |
| Title length | 61 no |
| Quoted title | "AP7AM | Latest Telugu News | Trusted by Lakhs of News Readers" |
| Meta description | "Get the latest Telugu news, breaking stories, politics, and entertainment updates on AP7AM. Fast and reliable news trusted by lakhs of readers." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1 |
| Canonical | https://www.ap7am.com |
| Language | en |
| Links | 176 |
| Images | 83 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for ap7am.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
ap7am.com is placed in Frankfurt am Main, Germany.
ap7am.com expires on 5 June 2028 according to https://rdap.verisign.com/com/v1/domain/ap7am.com.
The registry did not return a person or a company for ap7am.com. RDAP often redacts the registrant. The registrar on file is Name.com, Inc..
No other indexable reports share this TLD, host, or registrar yet.
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.