insta.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
75
insta.com was registered on 19 Aug 1997 via Tucows Domains Inc. and the registry expiry is 18 Aug 2032. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/insta.com.
insta.com publishes 2 nameservers. DNSSEC is not signed.
insta.com has 1 IPv4 address (148.135.3.67). The geolocation database places 148.135.3.67 in Los Angeles, United States.
The TLS certificate from YE1 is valid and has 75 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for insta.com in the checks that ran.
insta.com was registered on 19 Aug 1997 via Tucows Domains Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/insta.com.
| Registered | since 19 Aug 1997 |
|---|---|
| Created | 19 August 1997 |
| Updated | 18 April 2025 |
| Expires | 18 August 2032 |
| Registrar | Tucows Domains Inc. |
| Status | active |
| Nameservers | dns.lig.net, dnse.lig.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/insta.com |
Nameserver dns.lig.net is published for insta.com in the registration record from https://rdap.verisign.com/com/v1/domain/insta.com.
Nameserver dnse.lig.net is published for insta.com in the registration record from https://rdap.verisign.com/com/v1/domain/insta.com.
insta.com has 1 address record, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 148.135.3.67 |
|---|---|
| AAAA | — |
| NS | dns.lig.net, dnse.lig.net |
| MX | mail.insta.com (5) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at insta.com is "v=spf1 mx ip4:148.135.3.67/24 -all".
The DMARC text record at _dmarc.insta.com is "v=DMARC1; p=reject; sp=none; fo=1; ri=3600; rua=mailto:[email protected]; ruf=mailto:sdw+[email protected]".
IPv4 address 148.135.3.67 answers for insta.com at resolver 1.1.1.1:53.
Mail exchanger mail.insta.com has preference 5.
insta.com is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 148.135.3.67 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
The certificate for insta.com is valid, with 75 days left and 65 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | lig.net |
| Valid from | 17 October 2026 |
| Valid until | 15 January 2027 |
| Days left | 75 |
| SAN count | 65 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: artisticwindow.com, ashburnva.com, bluescholar.africa, bluescholar.com, bluescholar.eu, bluescholar.in, bluescholar.org, bluescholar.uk, bluescholar.us, chat.lig.net, chat.mud.net, chat.openrob.com, chat.sdw.st, cped.co, dns.lig.net, g.sdw.st, insta.com, insta.org, ip.st, javaglue.com, javaglue.org, jenkins.lig.net, joshbryant.us, lig.net, ligemail.lig.net, miamisburg.com, mud.net, oliviawilliams.us, openpress.org, openrob.com, openta.org, optimalogic.com, pro-se.org, rachelnakooka.com, sdw.st, test.lig.net, u13g.com, volksdroid.com, volksdroid.org, w.lig.net, w.openrob.com, www.ashburnva.com, www.bluescholar.africa, www.bluescholar.com, www.bluescholar.eu, www.bluescholar.in, www.bluescholar.org, www.bluescholar.uk, www.bluescholar.us, www.cped.co, www.insta.com, www.insta.org, www.ip.st, www.lig.net, www.miamisburg.com, www.mud.net, www.oliviawilliams.us, www.openrob.com, www.openta.org, www.optimalogic.com, www.pro-se.org, www.rachelnakooka.com, www.sdw.st, www.u13g.com, xanderwilliams.us.
Tech detection checked the fetched homepage and named 1 product. Source: wappalyzergo.
Nginx is filed under Web servers, Reverse proxies.
The homepage returned HTTP 200 in 155 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 155 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 insta.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 10 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.
insta.com is placed in Los Angeles, United States.
insta.com expires on 18 August 2032 according to https://rdap.verisign.com/com/v1/domain/insta.com.
The registry did not return a person or a company for insta.com. RDAP often redacts the registrant. The registrar on file is Tucows Domains 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.