flightstatusalert.com - robtex.com
flightstatusalert.com
com
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gtld-servers.net β | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1776133967 | ||||||
Same first word
flightstatusalert.com |
DNS History
10 records (10 active, 0 former)
βNShuamei.ns.giantpanda.com2026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βNSyangguang.ns.giantpanda.com2026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA2600:3c03::f03c:95ff:fe00:29ca2026-04-14 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA2600:3c03::f03c:95ff:fe91:5d522026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA2600:3c03::f03c:95ff:feed:4d4f2026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA2600:3c03::f03c:95ff:feed:cf2a2026-04-14 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA45.33.83.1002026-04-14 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA45.79.167.1802026-04-14 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA66.175.209.1792026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
βA96.126.111.1652026-03-08 β 2026-04-14 Β· 2 obs
β 2026-04-14 02:52:54
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| flightstatusalert.com | yangguang.ns.giantpanda.com, huamei.ns.giantpanda.com | 2 records |
β Authoritative Response
Server:75.2.45.63
NS records: yangguang.ns.giantpanda.com, huamei.ns.giantpanda.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for flightstatusalert.com (unsigned zone)
β±οΈ Timing
Total: 104ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 66.175.209.179, 45.79.167.180... |
| AAAA | 4 | 2600:3c03::f03c:95ff:feed:cf2a, 2600:3c03::f03c:95ff:feed:4d4f... |
| SOA | 1 | huamei.ns.giantpanda.com admin.giantpand |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (yangguang.ns.giantpanda.com, huamei.ns.giantpanda.com)
Analysis
IP Addresses
Eight IP numbers are pointed to by flightstatusalert.com: 2600:3c03::f03c:95ff:fe00:29ca, 2600:3c03::f03c:95ff:fe91:5d52, 2600:3c03::f03c:95ff:feed:4d4f, 2600:3c03::f03c:95ff:feed:cf2a, 45.33.83.100, 45.79.167.180, 66.175.209.179 and 96.126.111.165.
Other host names such as link-offline.info, 148.clients.your-server.com, miks.it, tefi.it and 149.clients.your-server.com share IPs with flightstatusalert.com.
Name Servers
flightstatusalert.com is delegated to two name servers: huamei.ns.giantpanda.com and yangguang.ns.giantpanda.com.
flightstatusalert.com shares the same name server setup as m203-gim.yearlyloans.com, mail.namenoir.com, checkcourts.com, productfeedtool.com and ns2.filmsubtitle.com.
flightstatusalert.com at least partially shares name servers with other domains, for instance darksonic.de, spansko.com, vodi.net, temozon.com and churchconsultants.com.
These name servers are commonly used with damao.ns.giantpanda.com, taishan.ns.giantpanda.com, lunlun.ns.giantpanda.com, yangyang.ns.giantpanda.com, yunzi.ns.giantpanda.com and zhenzhen.ns.giantpanda.com.
Host names with a single IP:
huamei.ns.giantpanda.com points to 3.33.232.36.
yangguang.ns.giantpanda.com points to 75.2.45.63.