longnet.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
66
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
66
longnet.net was registered on 10 Apr 2002 via Network Solutions, LLC and the registry expiry is 10 Apr 2027. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/longnet.net.
longnet.net publishes 4 nameservers. DNSSEC is not signed.
longnet.net has 1 IPv4 address (20.40.247.242). The geolocation database places 20.40.247.242 in Des Moines, United States.
The TLS certificate from DigiCert Global G2 TLS RSA SHA256 2020 CA1 is valid and has 7 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named IIS, Microsoft ASP.NET and Windows Server. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for longnet.net in the checks that ran.
longnet.net was registered on 10 Apr 2002 via Network Solutions, LLC. The registry returned 1 status value and 4 nameservers from https://rdap.verisign.com/net/v1/domain/longnet.net.
| Registered | since 10 Apr 2002 |
|---|---|
| Created | 10 April 2002 |
| Updated | 1 February 2024 |
| Expires | 10 April 2027 |
| Registrar | Network Solutions, LLC |
| Status | client transfer prohibited |
| Nameservers | ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/longnet.net |
longnet.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.
Nameserver ns1-06.azure-dns.com is published for longnet.net in the registration record from https://rdap.verisign.com/net/v1/domain/longnet.net.
Nameserver ns2-06.azure-dns.net is published for longnet.net in the registration record from https://rdap.verisign.com/net/v1/domain/longnet.net.
Nameserver ns3-06.azure-dns.org is published for longnet.net in the registration record from https://rdap.verisign.com/net/v1/domain/longnet.net.
Nameserver ns4-06.azure-dns.info is published for longnet.net in the registration record from https://rdap.verisign.com/net/v1/domain/longnet.net.
longnet.net has 1 address record, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 20.40.247.242 |
|---|---|
| AAAA | — |
| NS | ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info |
| MX | longnet-net.mail.protection.outlook.com (5) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at longnet.net is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 20.40.247.242 answers for longnet.net at resolver 1.1.1.1:53.
Mail exchanger longnet-net.mail.protection.outlook.com has preference 5. The host is recognised as Microsoft 365.
A random label under longnet.net also resolved, which means wildcard DNS is on.
longnet.net is placed in Des Moines, United States by the local geolocation database (db-ip).
| Address | 20.40.247.242 |
|---|---|
| Country | United States |
| City | Des Moines |
| Source | db-ip |
The certificate for longnet.net is valid, with 7 days left and 6 subject alternative names. Source: tls:443.
| Issuer | DigiCert Global G2 TLS RSA SHA256 2020 CA1 |
|---|---|
| Subject | www.longnet.net |
| Valid from | 23 April 2026 |
| Valid until | 7 November 2026 |
| Days left | 7 |
| SAN count | 6 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: longadvantage.com, longnet.net, longrealtyonline.com, www.longadvantage.com, www.longnet.net, www.longrealtyonline.com.
Tech detection checked the fetched homepage and named 3 products. Source: wappalyzergo.
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 0 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 0 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for longnet.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 | 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 16 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 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.
longnet.net is placed in Des Moines, United States.
longnet.net expires on 10 April 2027 according to https://rdap.verisign.com/net/v1/domain/longnet.net.
The registry did not return a person or a company for longnet.net. RDAP often redacts the registrant. The registrar on file is Network Solutions, 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.