Check DNS, Urls + Redirects, Certificates and Content of your Website




X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
05.08.2022 19:27:05


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
inscrpcion.uepbi.com

Name Error
yes
1
0
www.inscrpcion.uepbi.com

Name Error
yes
1
0
*.uepbi.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.inscrpcion.uepbi.com
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 20826, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.08.2022, 00:00:00 +, Signature-Inception: 31.07.2022, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: com
com
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest 4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 17:00:00 +, Signature-Inception: 05.08.2022, 16:00:00 +, KeyTag 20826, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20826 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 30909, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 32298, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 18:24:21 +, Signature-Inception: 03.08.2022, 18:19:21 +, KeyTag 30909, Signer-Name: com



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 30909 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 30909, DigestType 2 and Digest "4tPJFvbe6scylOgmj7WIUESoM/xUWViPSpGEz8QaV2Y=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: uepbi.com
uepbi.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "v50eq6ajom2uaunbj7duuje9g2l9ioqb" between the hashed NSEC3-owner "v50ebm83oek8aj856chq5hpc5dcjndnf" and the hashed NextOwner "v50faso4ufjdnurrj2rs3hbineh6rk72". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner v50ebm83oek8aj856chq5hpc5dcjndnf.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 11.08.2022, 05:52:37 +, Signature-Inception: 04.08.2022, 04:42:37 +, KeyTag 32298, Signer-Name: com



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ck0pojmg874ljref7efn8430qvit8bsm" as Owner. That's the Hash of "com" with the NextHashedOwnerName "ck0q2d6ni4i7eqh8na30ns61o48ul8g5". So that domain name is the Closest Encloser of "uepbi.com". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ck0pojmg874ljref7efn8430qvit8bsm.com., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 11.08.2022, 04:24:10 +, Signature-Inception: 04.08.2022, 03:14:10 +, KeyTag 32298, Signer-Name: com



3 DNSKEY RR found



Public Key with Algorithm 13, KeyTag 1556, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 13, KeyTag 15901, Flags 256



Public Key with Algorithm 13, KeyTag 49595, Flags 257 (SEP = Secure Entry Point)



3 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner uepbi.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 26.08.2022, 08:06:36 +, Signature-Inception: 27.07.2022, 07:54:00 +, KeyTag 1556, Signer-Name: uepbi.com



RRSIG-Owner uepbi.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 26.08.2022, 08:06:36 +, Signature-Inception: 27.07.2022, 07:54:00 +, KeyTag 15901, Signer-Name: uepbi.com



RRSIG-Owner uepbi.com., Algorithm: 13, 2 Labels, original TTL: 86400 sec, Signature-expiration: 26.08.2022, 08:06:36 +, Signature-Inception: 27.07.2022, 07:54:00 +, KeyTag 49595, Signer-Name: uepbi.com



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 1556 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 15901 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 13 and DNSKEY with KeyTag 49595 used to validate the DNSKEY RRSet



Error: DNSKEY 1556 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Error: DNSKEY 15901 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Error: DNSKEY 49595 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.

Zone: inscrpcion.uepbi.com
inscrpcion.uepbi.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "uepbi.com" and the NextOwner "_acme-challenge.uepbi.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "inscripcion.uepbi.com" and the NextOwner "ipv4.uepbi.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC

Zone: www.inscrpcion.uepbi.com
www.inscrpcion.uepbi.com
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "uepbi.com" and the NextOwner "_acme-challenge.uepbi.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, NSEC, DNSKEY



DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "inscripcion.uepbi.com" and the NextOwner "ipv4.uepbi.com". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: A, RRSIG, NSEC


3. Name Servers

DomainNameserverNS-IP
www.inscrpcion.uepbi.com
  ns2.uepbi.com

inscrpcion.uepbi.com
  ns2.uepbi.com

uepbi.com
  ns1.smartnetsystem.us
74.208.32.33
Philadelphia/Pennsylvania/United States (US) - IONOS SE


  ns1.uepbi.com
74.208.32.33
Philadelphia/Pennsylvania/United States (US) - IONOS SE


  ns2.smartnetsystem.us
74.208.32.33
Philadelphia/Pennsylvania/United States (US) - IONOS SE


  ns2.uepbi.com
74.208.32.33
Philadelphia/Pennsylvania/United States (US) - IONOS SE

com
  a.gtld-servers.net / nnn1-stk4


  b.gtld-servers.net / nnn1-eltxl2


  c.gtld-servers.net / nnn1-stk4


  d.gtld-servers.net / nnn1-stk4


  e.gtld-servers.net / nnn1-stk4


  f.gtld-servers.net / nnn1-fra5


  g.gtld-servers.net / nnn1-fra5


  h.gtld-servers.net / nnn1-fra5


  i.gtld-servers.net / nnn1-fra5


  j.gtld-servers.net / nnn1-lon5


  k.gtld-servers.net / nnn1-lon5


  l.gtld-servers.net / nnn1-lon5


  m.gtld-servers.net / nnn1-lon5


4. SOA-Entries


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1659720396
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:2


Domain:com
Zone-Name:com
Primary:a.gtld-servers.net
Mail:nstld.verisign-grs.com
Serial:1659720411
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:11


Domain:uepbi.com
Zone-Name:uepbi.com
Primary:ns2.uepbi.com
Mail:norkisp.gmail.com
Serial:2022080501
Refresh:10800
Retry:3600
Expire:604800
TTL:10800
num Entries:4


Domain:inscrpcion.uepbi.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.inscrpcion.uepbi.com
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "inscrpcion.uepbi.com" is subdomain, public suffix is ".com", top-level-domain is ".com", top-level-domain-type is "generic", tld-manager is "VeriSign Global Registry Services", num .com-domains preloaded: 63591 (complete: 175327)
AGood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. Header-Checks


3. DNS- and NameServer - Checks

AInfo:: 72 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 72 Queries complete, 66 with IPv6, 6 with IPv4.
Warning: Only some DNS Queries done via ipv6. IPv6 is the future, so the name servers of your name servers should have ipv6 addresses.
Bad (greater 8):: An average of 18.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.smartnetsystem.us, ns1.uepbi.com, ns2.smartnetsystem.us, ns2.uepbi.com, 2 Name Servers included in Delegation: ns1.smartnetsystem.us, ns2.smartnetsystem.us, 2 Name Servers included in 1 Zone definitions: ns1.uepbi.com, ns2.uepbi.com, 1 Name Servers listed in SOA.Primary: ns2.uepbi.com.
AGood: Only one SOA.Primary Name Server found.: ns2.uepbi.com.
Error: SOA.Primary Name Server not included in the delegation set.: ns2.uepbi.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.smartnetsystem.us (74.208.32.33): Delegation: ns1.smartnetsystem.us, ns2.smartnetsystem.us, Zone: ns1.uepbi.com, ns2.uepbi.com. Name Servers defined in Delegation, missing in Zone: ns1.smartnetsystem.us, ns2.smartnetsystem.us.Name Servers defined in Zone, missing in Delegation: ns1.uepbi.com, ns2.uepbi.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns1.uepbi.com (74.208.32.33): Delegation: ns1.smartnetsystem.us, ns2.smartnetsystem.us, Zone: ns1.uepbi.com, ns2.uepbi.com. Name Servers defined in Delegation, missing in Zone: ns1.smartnetsystem.us, ns2.smartnetsystem.us.Name Servers defined in Zone, missing in Delegation: ns1.uepbi.com, ns2.uepbi.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.smartnetsystem.us (74.208.32.33): Delegation: ns1.smartnetsystem.us, ns2.smartnetsystem.us, Zone: ns1.uepbi.com, ns2.uepbi.com. Name Servers defined in Delegation, missing in Zone: ns1.smartnetsystem.us, ns2.smartnetsystem.us.Name Servers defined in Zone, missing in Delegation: ns1.uepbi.com, ns2.uepbi.com.
XFatal: Inconsistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Read https://www.iana.org/help/nameserver-requirements and send it to your Name Server Hoster.: ns2.uepbi.com (74.208.32.33): Delegation: ns1.smartnetsystem.us, ns2.smartnetsystem.us, Zone: ns1.uepbi.com, ns2.uepbi.com. Name Servers defined in Delegation, missing in Zone: ns1.smartnetsystem.us, ns2.smartnetsystem.us.Name Servers defined in Zone, missing in Delegation: ns1.uepbi.com, ns2.uepbi.com.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 74., 1 different subnets (first two Bytes): 74.208., 1 different subnets (first three Bytes): 74.208.32.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns2.uepbi.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
Nameserver doesn't pass all EDNS-Checks: ns2.uepbi.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

4. Content- and Performance-critical Checks

AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 62926 milliseconds, 62.926 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > of the last months are listed

Small Code Update - wait one minute


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.smartnetsystem.us, ns1.uepbi.com, ns2.smartnetsystem.us, ns2.uepbi.com

QNr.DomainTypeNS used
1
us
NS
k.root-servers.net (2001:7fd::1)

Answer: b.cctld.us, f.cctld.us, k.cctld.us, w.cctld.us, x.cctld.us, y.cctld.us
2
ns1.smartnetsystem.us
NS
b.cctld.us (2001:502:ad09::29)

Answer: 9a02168.online-server.cloud, armxus.com, ns1.armxus.com, ns2.armxus.com
3
com
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
4
ns1.uepbi.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.smartnetsystem.us, ns2.smartnetsystem.us
5
ns2.smartnetsystem.us
NS
b.cctld.us (2001:502:ad09::29)

Answer: 9a02168.online-server.cloud, armxus.com, ns1.armxus.com, ns2.armxus.com
6
ns2.uepbi.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns1.smartnetsystem.us, ns2.smartnetsystem.us
7
cloud
NS
d.root-servers.net (2001:500:2d::d)

Answer: a.nic.cloud, b.nic.cloud, c.nic.cloud, d.nic.cloud
8
9a02168.online-server.cloud
NS
a.nic.cloud (2001:dcd:1::10)

Answer: ns-1and1.ui-dns.biz, ns-1and1.ui-dns.com, ns-1and1.ui-dns.de, ns-1and1.ui-dns.org
9
armxus.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: 9a02168.online-server.cloud, ns1.armxus.com, ns2.armxus.com, ns2.smartnetsystem.us

Answer: ns1.armxus.com
74.208.32.33

Answer: ns2.armxus.com
74.208.32.33
10
biz
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld.biz, b.gtld.biz, c.gtld.biz, w.gtld.biz, x.gtld.biz, y.gtld.biz
11
ns-1and1.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
12
ns-1and1.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
13
de
NS
l.root-servers.net (2001:500:9f::42)

Answer: a.nic.de, f.nic.de, l.de.net, n.de.net, s.de.net, z.nic.de
14
ns-1and1.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
15
org
NS
d.root-servers.net (2001:500:2d::d)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
16
ns-1and1.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
17
ns-biz.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
18
ns-biz.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
19
ns-biz.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
20
ns-com.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
21
ns-com.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
22
ns-com.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
23
ns-de.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
24
ns-de.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
25
ns-de.ui-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns-org.ui-dns.biz, ns-org.ui-dns.com, ns-org.ui-dns.de, ns-org.ui-dns.org

Answer: ns-org.ui-dns.org
2001:8d8:fe:53:0:d9a0:53c4:100, 217.160.83.196
26
ns-org.ui-dns.biz
NS
a.gtld.biz (2001:502:ad09::30)

Answer: ns-biz.ui-dns.biz, ns-biz.ui-dns.com, ns-biz.ui-dns.de, ns-biz.ui-dns.org

Answer: ns-biz.ui-dns.biz
2001:8d8:fe:53:0:d9a0:51c3:100, 217.160.81.195
27
ns-org.ui-dns.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns-com.ui-dns.biz, ns-com.ui-dns.com, ns-com.ui-dns.de, ns-com.ui-dns.org

Answer: ns-com.ui-dns.com
2001:8d8:fe:53:0:d9a0:52c2:100, 217.160.82.194
28
ns-org.ui-dns.de
NS
a.nic.de (2001:678:2::53)

Answer: ns-de.ui-dns.biz, ns-de.ui-dns.com, ns-de.ui-dns.de, ns-de.ui-dns.org

Answer: ns-de.ui-dns.de
2001:8d8:fe:53:0:d9a0:50c1:100, 217.160.80.193
29
armxus.com: 74.208.32.33
A
ns1.armxus.com (74.208.32.33)
30
armxus.com: 2607:f1c0:1800:81eb::1
AAAA
ns1.armxus.com (74.208.32.33)
31
ns-1and1.ui-dns.biz: 217.160.81.200
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
32
ns-1and1.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c8:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
33
9a02168.online-server.cloud: 74.208.32.33
A
ns-1and1.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c8:100)
34
9a02168.online-server.cloud: 2607:f1c0:1800:81eb::1
AAAA
ns-1and1.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c8:100)
35
ns-1and1.ui-dns.com: 217.160.82.200
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
36
ns-1and1.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c8:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
37
ns-1and1.ui-dns.de: 217.160.80.200
A
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
38
ns-1and1.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c8:100
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
39
ns-1and1.ui-dns.org: 217.160.83.200
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
40
ns-1and1.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c8:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
41
ns-biz.ui-dns.com: 217.160.82.195
A
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
42
ns-biz.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c3:100
AAAA
ns-com.ui-dns.com (2001:8d8:fe:53:0:d9a0:52c2:100)
43
ns-biz.ui-dns.de: 185.132.32.195, 217.160.80.195
A
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
44
ns-biz.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c3:100, 2607:f1c0:fe:53:185:132:32:195
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
45
ns-biz.ui-dns.org: 217.160.83.195
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
46
ns-biz.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c3:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
47
ns-com.ui-dns.biz: 217.160.81.194
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
48
ns-com.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c2:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
49
ns-com.ui-dns.de: 185.132.32.194, 217.160.80.194
A
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
50
ns-com.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c2:100, 2607:f1c0:fe:53:185:132:32:194
AAAA
ns-de.ui-dns.de (2001:8d8:fe:53:0:d9a0:50c1:100)
51
ns-com.ui-dns.org: 217.160.83.194
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
52
ns-com.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c2:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
53
ns-de.ui-dns.biz: 217.160.81.193
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
54
ns-de.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c1:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
55
ns-de.ui-dns.com: 217.160.82.193
A
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
56
ns-de.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c1:100
AAAA
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
57
ns-de.ui-dns.org: 217.160.83.193
A
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
58
ns-de.ui-dns.org: 2001:8d8:fe:53:0:d9a0:53c1:100
AAAA
ns-org.ui-dns.org (2001:8d8:fe:53:0:d9a0:53c4:100)
59
ns-org.ui-dns.biz: 217.160.81.196
A
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
60
ns-org.ui-dns.biz: 2001:8d8:fe:53:0:d9a0:51c4:100
AAAA
ns-biz.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c3:100)
61
ns-org.ui-dns.com: 217.160.82.196
A
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
62
ns-org.ui-dns.com: 2001:8d8:fe:53:0:d9a0:52c4:100
AAAA
ns-com.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c2:100)
63
ns-org.ui-dns.de: 217.160.80.196
A
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
64
ns-org.ui-dns.de: 2001:8d8:fe:53:0:d9a0:50c4:100
AAAA
ns-de.ui-dns.biz (2001:8d8:fe:53:0:d9a0:51c1:100)
65
ns1.smartnetsystem.us: 74.208.32.33
A
9a02168.online-server.cloud (2607:f1c0:1800:81eb::1)
66
ns1.smartnetsystem.us: No AAAA record found
AAAA
9a02168.online-server.cloud (2607:f1c0:1800:81eb::1)
67
ns1.uepbi.com: 74.208.32.33
A
ns1.smartnetsystem.us (74.208.32.33)
68
ns1.uepbi.com: No AAAA record found
AAAA
ns1.smartnetsystem.us (74.208.32.33)
69
ns2.smartnetsystem.us: 74.208.32.33
A
9a02168.online-server.cloud (2607:f1c0:1800:81eb::1)
70
ns2.smartnetsystem.us: No AAAA record found
AAAA
9a02168.online-server.cloud (2607:f1c0:1800:81eb::1)
71
ns2.uepbi.com: 74.208.32.33
A
ns1.smartnetsystem.us (74.208.32.33)
72
ns2.uepbi.com: No AAAA record found
AAAA
ns1.smartnetsystem.us (74.208.32.33)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
uepbi.com
0

no CAA entry found
1
0
com
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
uepbi.com
v=spf1 +a +mx +a:panel.armux.com -all
ok
1
0
_acme-challenge.inscrpcion.uepbi.com.uepbi.com

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=0a14a006-51db-4dc2-b4ad-90b6900c070d


Last Result: https://check-your-website.server-daten.de/?q=inscrpcion.uepbi.com - 2022-08-05 19:27:05


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=inscrpcion.uepbi.com" target="_blank">Check this Site: inscrpcion.uepbi.com</a>

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro