pdfwifi.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
65
pdfwifi.com was registered on 16 May 2019 via Amazon Registrar, Inc. and the registry expiry is 16 May 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
pdfwifi.com publishes 4 nameservers. DNSSEC is not signed.
pdfwifi.com has 1 IPv4 address (34.49.55.196). The geolocation database places 34.49.55.196 in Kansas City, United States.
The TLS certificate from WR3 is valid and has 82 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google Cloud, Google Cloud CDN, HTTP/3, Next.js, Node.js, React and Webpack. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for pdfwifi.com in the checks that ran.
pdfwifi.com was registered on 16 May 2019 via Amazon Registrar, Inc.. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
| Registered | since 16 May 2019 |
|---|---|
| Created | 16 May 2019 |
| Updated | 16 May 2026 |
| Expires | 16 May 2027 |
| Registrar | Amazon Registrar, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/pdfwifi.com |
pdfwifi.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 ns-cloud-c1.googledomains.com is published for pdfwifi.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
Nameserver ns-cloud-c2.googledomains.com is published for pdfwifi.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
Nameserver ns-cloud-c3.googledomains.com is published for pdfwifi.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
Nameserver ns-cloud-c4.googledomains.com is published for pdfwifi.com in the registration record from https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
pdfwifi.com has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 34.49.55.196 |
|---|---|
| AAAA | — |
| NS | ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c4.googledomains.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 34.49.55.196 answers for pdfwifi.com at resolver 1.1.1.1:53.
pdfwifi.com is placed in Kansas City, United States by the local geolocation database (db-ip).
| Address | 34.49.55.196 |
|---|---|
| Country | United States |
| City | Kansas City |
| Source | db-ip |
The certificate for pdfwifi.com is valid, with 82 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WR3 |
|---|---|
| Subject | pdfwifi.com |
| Valid from | 23 October 2026 |
| Valid until | 21 January 2027 |
| Days left | 82 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: pdfwifi.com.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Google Cloud is filed under IaaS.
Google Cloud CDN is filed under CDN.
HTTP/3 is filed under Miscellaneous.
Next.js is filed under JavaScript frameworks, Web frameworks.
Node.js is filed under Programming languages.
React is filed under JavaScript frameworks.
Webpack is filed under Miscellaneous.
The homepage returned HTTP 200 in 140 ms. The target title is 23 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 140 ms |
| Title length | 23 yes |
| Quoted title | "Wi-Fi Transfer QR login" |
| Meta description | "Transfer music, videos, photos or documents from your iPhone or iPad to a Mac or PC and vice versa with our super fast Wi-Fi Transfer technology. Just fire up a camera and your files are one tap away." yes |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 1 |
| Images | 1 |
| 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 pdfwifi.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 | no |
| 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 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.
pdfwifi.com is placed in Kansas City, United States.
pdfwifi.com expires on 16 May 2027 according to https://rdap.verisign.com/com/v1/domain/pdfwifi.com.
The registry did not return a person or a company for pdfwifi.com. RDAP often redacts the registrant. The registrar on file is Amazon Registrar, 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.