dns.pizza
Domain Intelligence Report

segment.com

Compare

IPv6

Measured 2026-11-01 11:10 UTC · aaaa.bot
D

The website has no IPv6.

segment.com has no IPv6 address published.

  • ✗ segment.com: no IPv6 address
  • ✗ www.segment.com: no IPv6 address
  • ✓ Mail: 1 of 1 servers have IPv6
  • ✓ Nameservers: 4 of 4 have IPv6
Details: published addresses and what answered
segment.comPublishedno IPv6 address publishedAnswers when we connectnothing to test
www.segment.comPublishedno IPv6 address publishedAnswers when we connectnothing to test
MailPublishedsmtp.google.comAnswers when we connect✓ has IPv6
NameserversPublishedns-1205.awsdns-22.orgns-1681.awsdns-18.co.ukns-386.awsdns-48.comns-677.awsdns-20.netAnswers when we connect✓ has IPv6✓ has IPv6✓ has IPv6✓ has IPv6
First measured 2026-11-01: no IPv6 publishedIf this changes, the date will appear here.
Full check on aaaa.bot →Permanent receipt zMoNR9UB_0JSON

Lineage

Our records: Jan 7, 2009 → Nov 1, 2026

Oldest registry snapshot we hold: 2012 · 3 renewals on record · DNS at Amazon Route 53 · 11 nameserver changes seen. These dates are when our records begin, not when the domain was registered.

Registrar
226 snapshots
GoDaddy.com, LLCRenewed +1 yearbetween Nov 26, 2012 and Nov 30, 2012Expiry moved from 2015-07-05 to 2016-07-04.Renewed +9 yearsbetween Dec 20, 2012 and Jul 26, 2016Expiry moved from 2016-07-04 to 2025-07-05, at GoDaddy.com, LLC.Moved to MarkMonitor, Incbetween May 13, 2022 and Jun 20, 2022From GoDaddy.com, LLC to MarkMonitor, Inc, with 1 year added. Expiry moved from 2025-07-04 to 2026-07-05.
Nameservers
registry zone files
DNS moved to GoDaddybetween Apr 21, 2014 and May 1, 2014jill.ns.cloudflare.com, seth.ns.cloudflare.com → ns23.domaincontrol.com, ns24.domaincontrol.com. Old set last seen in WHOIS on 2014-04-21; new set first in the registry zone file on 2014-05-01.
seen in WHOIS
Amazon Route 53DNS moved to dsredirection.combetween Jan 9, 2009 and May 26, 2009dns1.ireithost.com, dns2.ireithost.com → ns1.dsredirection.com, ns2.dsredirection.com. Old set last seen in WHOIS on 2009-01-09; new set first seen in WHOIS on 2009-05-26.DNS moved to sendori.combetween Jul 25, 2009 and Jan 5, 2010ns1.dsredirection.com, ns2.dsredirection.com → dns1.sendori.com, dns2.sendori.com. Old set last seen in WHOIS on 2009-07-25; new set first seen in WHOIS on 2010-01-05.DNS moved to fastpark.netbetween Jan 5, 2010 and Jan 22, 2010dns1.sendori.com, dns2.sendori.com → ns1.fastpark.net, ns2.fastpark.net. Old set last seen in WHOIS on 2010-01-05; new set first seen in WHOIS on 2010-01-22.DNS moved to inavit.combetween Jan 30, 2011 and May 17, 2011ns1.fastpark.net, ns2.fastpark.net → dns1.inavit.com, dns2.inavit.com. Old set last seen in WHOIS on 2011-01-30; new set first seen in WHOIS on 2011-05-17.DNS moved to fastpark.netbetween Oct 24, 2011 and Jan 22, 2012dns1.inavit.com, dns2.inavit.com → ns1.fastpark.net, ns2.fastpark.net. Old set last seen in WHOIS on 2011-10-24; new set first seen in WHOIS on 2012-01-22.DNS moved to Cloudflarebetween Nov 26, 2012 and Nov 30, 2012ns1.fastpark.net, ns2.fastpark.net → jill.ns.cloudflare.com, seth.ns.cloudflare.com. Old set last seen in WHOIS on 2012-11-26; new set first seen in WHOIS on 2012-11-30.DNS moved to Amazon Route 53between May 1, 2014 and May 12, 2014ns23.domaincontrol.com, ns24.domaincontrol.com → ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net. Old set last in the registry zone file on 2014-05-01; new set first seen in WHOIS on 2014-05-12.DNS moved to GoDaddybetween May 12, 2014 and May 15, 2014ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net → ns27.domaincontrol.com, ns28.domaincontrol.com. Old set last seen in WHOIS on 2014-05-12; new set first seen in WHOIS on 2014-05-15.DNS moved to Amazon Route 53between Jun 1, 2014 and Oct 14, 2014ns27.domaincontrol.com, ns28.domaincontrol.com → ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net. Old set last in the registry zone file on 2014-06-01; new set first seen in WHOIS on 2014-10-14.New nameservers at Amazon Route 53between Jan 8, 2018 and Feb 26, 2018ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net → ns-1205.awsdns-22.org, ns-1681.awsdns-18.co.uk, ns-386.awsdns-48.com, ns-677.awsdns-20.net. Old set last seen in WHOIS on 2018-01-08; new set first seen in WHOIS on 2018-02-26.
IPv6
aaaa.bot check
2013201720212026
What changed (latest 8 of 15)
  1. IPv6 first measured: no IPv6 published on Nov 1, 2026segment.com: no IPv6 published. Grade D. Measured by aaaa.bot, 2026-11-01 11:10 UTC. No earlier IPv6 record is held, so this is not a "gained" date.
  2. Moved to MarkMonitor, Inc between May 13, 2022 and Jun 20, 2022From GoDaddy.com, LLC to MarkMonitor, Inc, with 1 year added. Expiry moved from 2025-07-04 to 2026-07-05.
  3. New nameservers at Amazon Route 53 between Jan 8, 2018 and Feb 26, 2018ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net → ns-1205.awsdns-22.org, ns-1681.awsdns-18.co.uk, ns-386.awsdns-48.com, ns-677.awsdns-20.net. Old set last seen in WHOIS on 2018-01-08; new set first seen in WHOIS on 2018-02-26.
  4. Renewed +9 years between Dec 20, 2012 and Jul 26, 2016Expiry moved from 2016-07-04 to 2025-07-05, at GoDaddy.com, LLC.
  5. DNS moved to Amazon Route 53 between Jun 1, 2014 and Oct 14, 2014ns27.domaincontrol.com, ns28.domaincontrol.com → ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net. Old set last in the registry zone file on 2014-06-01; new set first seen in WHOIS on 2014-10-14.
  6. DNS moved to GoDaddy between May 12, 2014 and May 15, 2014ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net → ns27.domaincontrol.com, ns28.domaincontrol.com. Old set last seen in WHOIS on 2014-05-12; new set first seen in WHOIS on 2014-05-15.
  7. DNS moved to Amazon Route 53 between May 1, 2014 and May 12, 2014ns23.domaincontrol.com, ns24.domaincontrol.com → ns-1124.awsdns-12.org, ns-1917.awsdns-47.co.uk, ns-242.awsdns-30.com, ns-950.awsdns-54.net. Old set last in the registry zone file on 2014-05-01; new set first seen in WHOIS on 2014-05-12.
  8. DNS moved to GoDaddy between Apr 21, 2014 and May 1, 2014jill.ns.cloudflare.com, seth.ns.cloudflare.com → ns23.domaincontrol.com, ns24.domaincontrol.com. Old set last seen in WHOIS on 2014-04-21; new set first in the registry zone file on 2014-05-01.

Registrar and renewals: 226 WHOIS/RDAP snapshots, 2012-09-05 to 2026-05-17 (ledger built 2026-09-27). Every renewal

Nameservers, registry zone files: 106 .com zone-file snapshots held, 2013-10-18 to 2026-11-01.

Nameservers, WHOIS snapshots: 258 WHOIS/RDAP snapshots that listed nameservers, 2009-01-07 to 2026-05-17 (who.is archive). A change is placed between the nearest observations on either side, from whichever source made them; where the two sources disagree, both are shown.

Hatched = the span we hold records for. A coloured bar runs only between observations that named the same registrar or operator; nothing is assumed in between.

Each mark sits at the first observation of the new state; its bracket runs back to the last observation of the old one.

Gathering intelligence... (12/12)
DNS
WHOIS
Security
Email
DNSSEC
Threats
Deliverability
SSL/TLS
HTTP
Tech Stack
Subdomains
Archive
Safe
DNSSEC unsigned
no attacks or spoofing
Up
HTTP 200
reachable and responding
Right
Set up Page Watch
it is what it is
Ready
135d ahead
you see what's coming
Outline
WHOIS
MarkMonitor Inc. · registered 28 years ago · expires Jul 5, 2028
DNS
3 A · 1 MX · 4 NS · 3 PTR · 1 SOA · 23 TXT
SSL/TLS
Amazon · TLSv1.3 · expires in 135d · 4 SANs
Email Auth
SPF ✓ · DKIM ✓ · DMARC ✓ (p=reject)
DNSSEC
not signed
Tech Stack
Host: Amazon Web Services · Email: Google Workspace · DNS: AWS Route 53
HTTP
2 redirect → 200 · HSTS ✗ · CSP ✗ · X-Frame ✗ · Nosniff ✗
Security
B (155/215) · 1 critical · 2 high
Threats
risk: none
Deliverability
A (94/100) · 1 MX · 9 IPs · 2 issue(s)
Subdomains
3 found · 78 answered (34 timed out) — email, static, www
Web Archive
no snapshots found
DNS Recordschecked 14.1d ago
Details
3 A · 1 MX · 4 NS · 3 PTR · 1 SOA · 23 TXT
WHOISchecked 14.1d ago
Details
MarkMonitor Inc.
Registered 28 years ago
Expires Jul 5, 2028
Renewal history →
Then vs Nownew
Live check, not a pre-computed card: then from the Internet Archive, now from today’s site.
Now part of, or forwards to, another organisation. (vs the Internet Archive’s copy from Mar 2013)
Now: Software or technology · actively maintained (live check, Nov 1, 2026; AI-judged, likely, not verified)
Check what it is now →
SSL/TLSchecked 14.1d ago
Details
Valid certificate
Issuer: Amazon
Protocol: TLSv1.3
Expires in 135 days
4 SAN(s)
Securitychecked 14.1d ago
Details
B
155/215
1 critical2 high1 medium
Weakest: Record Security, Basic Security
Email Authchecked 14.1d ago
Details
SPFDKIMDMARC
Policy: reject
DNSSECchecked 14.1d ago
Details
Not DNSSEC-signed
Tech Stackchecked 14.1d ago
Details
Amazon Web ServicesEmail: Google WorkspaceDNS: AWS Route 53Google Search ConsoleAtlassianDocuSignHubSpot
HTTP / Headerschecked 14.1d ago
Details
2 redirect(s) → 200
HSTSCSPX-FrameNosniff
Threatschecked 14.1d ago
Details
Risk: none · score 0
Zone census
Subdomainschecked 14.1d ago
Details
3 found · 78 answered · 34 timed out (unknown)
emailstaticwww
Click a subdomain for its full report
Web Archivechecked 14.1d ago
Details
No archive snapshots found
Deliverabilitychecked 14.1d ago
Details
A
94/100 · 2 issue(s)
1 MX · 9 IP(s)

Want to know when segment.com changes?

Monitor it free — 50 monitors, uptime checks every 5 minutes, email alerts when something breaks. No card required.

Monitor segment.com

Explore related

Registered in 1998 — the same year as sharepoint.com, mozilla.org and medium.com.

AgeDomains from 1998TLD.com domainsRegistrarMarkMonitor Inc.DNS providerawsdns-18.co.uk nameserversDNS providerawsdns-20.net nameserversDNS providerawsdns-22.org nameserversDNS providerawsdns-48.com nameserversIPv6Does segment.com have IPv6?