emedpay.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
emedpay.net was registered on 7 Jun 2010 via GoDaddy.com, LLC and the registry expiry is 7 Jun 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/emedpay.net.
emedpay.net publishes 2 nameservers. DNSSEC is not signed.
emedpay.net has 1 IPv4 address (185.159.5.180). The geolocation database places 185.159.5.180 in Washington D.C., United States.
The TLS certificate from Starfield TLS Intermediate CA DV - R1v1 is valid and has 182 days left (TLS 1.2). The homepage answered HTTP 200.
Tech detection named HSTS, IIS, Microsoft ASP.NET and Windows Server. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for emedpay.net in the checks that ran.
emedpay.net was registered on 7 Jun 2010 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.verisign.com/net/v1/domain/emedpay.net.
| Registered | since 7 Jun 2010 |
|---|---|
| Created | 7 June 2010 |
| Updated | 7 June 2026 |
| Expires | 7 June 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns25.domaincontrol.com, ns26.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/emedpay.net |
emedpay.net carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
emedpay.net carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
emedpay.net 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.
emedpay.net carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns25.domaincontrol.com is published for emedpay.net in the registration record from https://rdap.verisign.com/net/v1/domain/emedpay.net.
Nameserver ns26.domaincontrol.com is published for emedpay.net in the registration record from https://rdap.verisign.com/net/v1/domain/emedpay.net.
emedpay.net has 1 address record, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.159.5.180 |
|---|---|
| AAAA | — |
| NS | ns25.domaincontrol.com, ns26.domaincontrol.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.159.5.180 answers for emedpay.net at resolver 1.1.1.1:53.
emedpay.net is placed in Washington D.C., United States by the local geolocation database (db-ip).
| Address | 185.159.5.180 |
|---|---|
| Country | United States |
| City | Washington D.C. |
| Source | db-ip |
The certificate for emedpay.net is valid, with 182 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Starfield TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | www.emedpay.net |
| Valid from | 15 October 2026 |
| Valid until | 1 May 2027 |
| Days left | 182 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: emedpay.net, www.emedpay.net.
Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.
HSTS is filed under Security.
IIS is filed under Web servers.
Microsoft ASP.NET is filed under Web frameworks.
Windows Server is filed under Operating systems.
The homepage returned HTTP 200 in 140 ms. The target title is 26 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 140 ms |
| Title length | 26 yes |
| Quoted title | "Welcome to www.emedpay.net" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| 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 emedpay.net 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 0 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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.
emedpay.net is placed in Washington D.C., United States.
emedpay.net expires on 7 June 2027 according to https://rdap.verisign.com/net/v1/domain/emedpay.net.
The registry did not return a person or a company for emedpay.net. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
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.