IPLIST.NET - snap1.api.no
Search for IP or hostnames:
snap1.api.no checked at 2025-09-16T19:45:50.165Z 563ms 66/66/66 100% R:17
snap1.api.no
NS | ns-bar.i.bitbit.net | ||||||
A | 2a02:c0:400:102::b 🇳🇴 Redpill Linpro | ||||||
PTR | ns-bar.local | ||||||
A | 87.238.39.51🇳🇴 Redpill Linpro | ||||||
PTR | ns-bar.i.bitbit.net | ||||||
NS | ns-foo.i.bitbit.net | ||||||
A | 2a02:c0:1001:1::2 🇳🇴 Redpill Linpro | ||||||
PTR | ns-foo.linpro.net | ||||||
A | 87.238.32.254🇳🇴 Redpill Linpro | ||||||
PTR | ns-foo.linpro.net | ||||||
NS | ns-zoo.i.bitbit.net | ||||||
A | 2600:3c00::f03c:91ff:febd:d3ff 🇺🇸 Linode AS63949 | ||||||
PTR | ns-zoo.i.bitbit.net | ||||||
A | 69.164.207.59🇺🇸 Linode AS63949 | ||||||
PTR | ns-zoo.i.bitbit.net |
api.no
NS | nsb.dnsnode.net | ||||||
NS | nsp.dnsnode.net | ||||||
NS | nsu.dnsnode.net | ||||||
MX | aspmx.l.google.com | ||||||
MX | alt1.aspmx.l.google.com | ||||||
MX | alt2.aspmx.l.google.com | ||||||
MX | alt3.aspmx.l.google.com | ||||||
MX | alt4.aspmx.l.google.com | ||||||
A | 2a02:c0:ac::e51:1 🇳🇴 Redpill Linpro | ||||||
A | 87.238.38.1🇳🇴 Redpill Linpro | ||||||
A | 87.238.38.2🇳🇴 Redpill Linpro |
rank #1140 in the tld
Up
bed.snap1.api.no |
varnish-general.snap1.api.no |
Starts with same word
Starts similarily
AI analysis
snap1.api.no
has children bed.snap1.api.no
and varnish-general.snap1.api.no
.
The zone for snap1.api.no
is delegated to three name servers: ns-bar.i.bitbit.net
, ns-foo.i.bitbit.net
, and ns-zoo.i.bitbit.net
.
snap1.api.no
at least partially shares name servers with other domains, including svg.redpill-linpro.com
, inderoyningen.no
, markedssjef.no
, nasport.no
, and linuxkurs.no
.
These name servers are commonly used alongside ns-foo.linpro.net
and ns-zoo.linpro.net
.
The host name ns-bar.i.bitbit.net
points to two IP numbers: 2a02:c0:400:102::b and 87.238.39.51. The host name ns-foo.i.bitbit.net
points to two IP numbers: 2a02:c0:1001:1::2 and 87.238.32.254. The host name ns-zoo.i.bitbit.net
points to two IP numbers: 2600:3c00::f03c:91ff:febd:d3ff and 69.164.207.59. No IP numbers are indicated as common across host names; overlaps, if any, are not specified.