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



X

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

Checked:
01.08.2020 09:32:43


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
gset.co.th
A

yes
1
0

AAAA

yes


www.gset.co.th

Name Error
yes
1
0
*.gset.co.th
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 46594, 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.2020, 00:00:00 +, Signature-Inception: 31.07.2020, 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: th
th
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 19117, DigestType 2 and Digest 4mvzX3MjSsUMYAYy/HF65JH0qLT2YvspI09Umaz+v2Q=



1 RRSIG RR to validate DS RR found



RRSIG-Owner th., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2020, 05:00:00 +, Signature-Inception: 01.08.2020, 04:00:00 +, KeyTag 46594, Signer-Name: (root)



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 37968, Flags 256



Public Key with Algorithm 8, KeyTag 59169, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner th., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 14.08.2020, 01:11:02 +, Signature-Inception: 30.07.2020, 04:00:12 +, KeyTag 19117, Signer-Name: th



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



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

Zone: co.th
co.th
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 8206, DigestType 2 and Digest YoiSESB1MsGDYfIB84BfyU9Y6V/bi0ftxDtz792WG34=



1 RRSIG RR to validate DS RR found



RRSIG-Owner co.th., Algorithm: 8, 2 Labels, original TTL: 7200 sec, Signature-expiration: 13.08.2020, 23:50:23 +, Signature-Inception: 30.07.2020, 04:00:12 +, KeyTag 59169, Signer-Name: th



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



3 DNSKEY RR found



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



Public Key with Algorithm 8, KeyTag 47580, Flags 256



Public Key with Algorithm 8, KeyTag 61728, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner co.th., Algorithm: 8, 2 Labels, original TTL: 43200 sec, Signature-expiration: 14.08.2020, 02:47:57 +, Signature-Inception: 30.07.2020, 04:00:37 +, KeyTag 8206, Signer-Name: co.th



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



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

Zone: gset.co.th
gset.co.th
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 "n57r65vf7nim8thj2a2lktrodmb6i998" between the hashed NSEC3-owner "mvluqg4ui07k42m4jbn5m5dg7u3s278i" and the hashed NextOwner "nd61gro9pc81057mlj5q0lk39658msqa". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner mvluqg4ui07k42m4jbn5m5dg7u3s278i.co.th., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 14.08.2020, 01:59:57 +, Signature-Inception: 30.07.2020, 04:00:37 +, KeyTag 47580, Signer-Name: co.th



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "mqcvqm9fefrnhob4hvfnl1ss9635eb5v" as Owner. That's the Hash of "co.th" with the NextHashedOwnerName "mv7431ag7vg3ch7382fvbrvi6kutesin". So that domain name is the Closest Encloser of "gset.co.th". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner mqcvqm9fefrnhob4hvfnl1ss9635eb5v.co.th., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 14.08.2020, 01:19:42 +, Signature-Inception: 30.07.2020, 04:00:37 +, KeyTag 47580, Signer-Name: co.th



0 DNSKEY RR found




Zone: www.gset.co.th
www.gset.co.th
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.gset.co.th
  ns1.bdm.microsoftonline.com

gset.co.th
  ns1.bdm.microsoftonline.com
40.90.4.208
Chicago/Illinois/United States (US) - Microsoft Corporation


 
2603:1061::d0
Chaoyang/Liaoning/China (CN) - Microsoft Corporation


  ns2.bdm.microsoftonline.com
64.4.48.208
Redmond/Washington/United States (US) - Microsoft Corporation


 
2620:1ec:8ec::d0
Toronto/Ontario/Canada (CA) - Microsoft Corporation


  ns3.bdm.microsoftonline.com
13.107.24.208
Ashburn/Virginia/United States (US) - Microsoft Corporation


 
2a01:111:4000::d0
Dublin/Leinster/Ireland (IE) - Microsoft Corporation


  ns4.bdm.microsoftonline.com
13.107.160.208
Ashburn/Virginia/United States (US) - Microsoft Corporation


 
2620:1ec:bda::d0
Redmond/Washington/United States (US) - Microsoft Corporation

co.th
  a.thains.co.th / BKK1
122.155.23.64
Samphanthawong/Bangkok/Thailand (TH) - CAT Telecom Public Company Limited


 
2001:c38:2000:183::30
Ratchathewi/Bangkok/Thailand (TH) - CAT Telecom Public Company Limited


  b.thains.co.th / Bkk2
203.159.64.64
Khlong Luang/Pathum Thani/Thailand (TH) - BKNIX


 
2001:c00:4618:3000::30
Watthana/Bangkok/Thailand (TH) - Internet Thailand Company Ltd.


T  c.thains.co.th
194.0.1.28
Nur-Sultan/Kazakhstan (KZ) - ICB plc Anycast (via NetConnex AS21396)


 
2001:678:4::1c
Lviv/L'vivs'ka Oblast'/Ukraine (UA) - Community DNS Limited


  ns.thnic.net
202.28.0.1
Bangkok/Thailand (TH) - THAINET


  p.thains.co.th / 1.ber.pch
204.61.216.126
Berkeley/California/United States (US) - WoodyNet


 
2001:500:14:6126:ad::1
Berkeley/California/United States (US) - WoodyNet

th
  a.thains.co.th / BKK1


  b.thains.co.th / Bkk2


T  c.thains.co.th


  ns.thnic.net


  p.thains.co.th / 2.ber.pch


4. SOA-Entries


Domain:th
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:th
Zone-Name:th
Primary:a.thains.co.th
Mail:registry.thains.co.th
Serial:1200801029
Refresh:1800
Retry:900
Expire:518400
TTL:1800
num Entries:1


Domain:th
Zone-Name:th
Primary:a.thains.co.th
Mail:registry.thains.co.th
Serial:1200801030
Refresh:1800
Retry:900
Expire:518400
TTL:1800
num Entries:3


Domain:co.th
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:co.th
Zone-Name:co.th
Primary:a.thains.co.th
Mail:registry.thains.co.th
Serial:1200801029
Refresh:1800
Retry:900
Expire:518400
TTL:1800
num Entries:2


Domain:co.th
Zone-Name:co.th
Primary:a.thains.co.th
Mail:registry.thains.co.th
Serial:1200801030
Refresh:1800
Retry:900
Expire:518400
TTL:1800
num Entries:6


Domain:gset.co.th
Zone-Name:gset.co.th
Primary:ns1.bdm.microsoftonline.com
Mail:azuredns-hostmaster.microsoft.com
Serial:1
Refresh:3600
Retry:300
Expire:2419200
TTL:300
num Entries:8


Domain:www.gset.co.th
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 "gset.co.th" is domain, public suffix is ".co.th", top-level-domain is ".th", top-level-domain-type is "country-code", Country is Thailand, tld-manager is "Thai Network Information Center Foundation", num .th-domains preloaded: 50 (complete: 128404)
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. DNS- and NameServer - Checks

AInfo:: 25 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 25 Queries complete, 17 with IPv6, 8 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.
Ok (4 - 8):: An average of 6.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, 4 Name Servers included in Delegation: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, 4 Name Servers included in 1 Zone definitions: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com, 1 Name Servers listed in SOA.Primary: ns1.bdm.microsoftonline.com.
AGood: Only one SOA.Primary Name Server found.: ns1.bdm.microsoftonline.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.bdm.microsoftonline.com.
AGood: Consistency 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. Ordered list of name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.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.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 4 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: microsoftonline.com
AGood: Name servers with different Country locations found: 4 Name Servers, 4 Countries: CA, CN, IE, US
AInfo: Ipv4-Subnet-list: 4 Name Servers, 3 different subnets (first Byte): 13., 40., 64., 3 different subnets (first two Bytes): 13.107., 40.90., 64.4., 4 different subnets (first three Bytes): 13.107.160., 13.107.24., 40.90.4., 64.4.48.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 3 different subnets (first block): 2603:, 2620:, 2a01:, 3 different subnets (first two blocks): 2603:1061:, 2620:01ec:, 2a01:0111:, 4 different subnets (first three blocks): 2603:1061:0000:, 2620:01ec:08ec:, 2620:01ec:0bda:, 2a01:0111:4000:, 4 different subnets (first four blocks): 2603:1061:0000:0000:, 2620:01ec:08ec:0000:, 2620:01ec:0bda:0000:, 2a01:0111:4000:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
XNameserver Timeout checking Echo Capitalization: c.thains.co.th
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
XNameserver Timeout checking EDNS512: c.thains.co.th / 194.0.1.28
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: c.thains.co.th: OP100: ok. FLAGS: fatal timeout. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: c.thains.co.th / 194.0.1.28: OP100: fatal timeout. FLAGS: ok. V1: ok. V1OP100: fatal timeout. V1FLAGS: ok. DNSSEC: fatal timeout. V1DNSSEC: fatal timeout. NSID: ok. COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns1.bdm.microsoftonline.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.

3. 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: 127823 milliseconds, 127.823 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" > 2019 are listed

No CRT - CT-Log entries found


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.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

QNr.DomainTypeNS used
1
com
NS
a.root-servers.net (2001:503:ba3e::2:30)

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
2
ns1.bdm.microsoftonline.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, nse24.o365filtering.com

Answer: ns1-34.azure-dns.com
150.171.10.34

Answer: nse12.o365filtering.com
104.47.38.8

Answer: nse13.o365filtering.com
104.47.2.8

Answer: nse21.o365filtering.com
104.47.40.8

Answer: nse24.o365filtering.com
104.47.121.8
3
ns2.bdm.microsoftonline.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, nse24.o365filtering.com

Answer: ns1-34.azure-dns.com
150.171.10.34

Answer: nse12.o365filtering.com
104.47.38.8

Answer: nse13.o365filtering.com
104.47.2.8

Answer: nse21.o365filtering.com
104.47.40.8

Answer: nse24.o365filtering.com
104.47.121.8
4
ns3.bdm.microsoftonline.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, nse24.o365filtering.com

Answer: ns1-34.azure-dns.com
150.171.10.34

Answer: nse12.o365filtering.com
104.47.38.8

Answer: nse13.o365filtering.com
104.47.2.8

Answer: nse21.o365filtering.com
104.47.40.8

Answer: nse24.o365filtering.com
104.47.121.8
5
ns4.bdm.microsoftonline.com
NS
b.gtld-servers.net (2001:503:231d::2:30)

Answer: ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org, ns4-34.azure-dns.info, nse12.o365filtering.com, nse13.o365filtering.com, nse21.o365filtering.com, nse24.o365filtering.com

Answer: ns1-34.azure-dns.com
150.171.10.34

Answer: nse12.o365filtering.com
104.47.38.8

Answer: nse13.o365filtering.com
104.47.2.8

Answer: nse21.o365filtering.com
104.47.40.8

Answer: nse24.o365filtering.com
104.47.121.8
6
net
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
7
ns2-34.azure-dns.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: ns2-01.azure-dns.net, ns2-02.azure-dns.net, ns2-03.azure-dns.net, ns2-04.azure-dns.net

Answer: ns2-01.azure-dns.net
2620:1ec:8ec::1, 64.4.48.1

Answer: ns2-02.azure-dns.net
2620:1ec:8ec::2, 64.4.48.2

Answer: ns2-03.azure-dns.net
2620:1ec:8ec::3, 64.4.48.3

Answer: ns2-04.azure-dns.net
2620:1ec:8ec::4, 64.4.48.4
8
org
NS
g.root-servers.net (2001:500:12::d0d)

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
9
ns3-34.azure-dns.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: ns3-01.azure-dns.org, ns3-02.azure-dns.org, ns3-03.azure-dns.org, ns3-04.azure-dns.org

Answer: ns3-01.azure-dns.org
13.107.24.1, 2a01:111:4000::1

Answer: ns3-02.azure-dns.org
13.107.24.2, 2a01:111:4000::2

Answer: ns3-03.azure-dns.org
13.107.24.3, 2a01:111:4000::3

Answer: ns3-04.azure-dns.org
13.107.24.4, 2a01:111:4000::4
10
info
NS
f.root-servers.net (2001:500:2f::f)

Answer: a0.info.afilias-nst.info, a2.info.afilias-nst.info, b0.info.afilias-nst.org, b2.info.afilias-nst.org, c0.info.afilias-nst.info, d0.info.afilias-nst.org
11
ns4-34.azure-dns.info
NS
a0.info.afilias-nst.info (2001:500:19::1)

Answer: ns4-01.azure-dns.info, ns4-02.azure-dns.info, ns4-03.azure-dns.info, ns4-04.azure-dns.info

Answer: ns4-01.azure-dns.info
13.107.160.1, 2620:1ec:bda::1

Answer: ns4-02.azure-dns.info
13.107.160.2, 2620:1ec:bda::2

Answer: ns4-03.azure-dns.info
13.107.160.3, 2620:1ec:bda::3

Answer: ns4-04.azure-dns.info
13.107.160.4, 2620:1ec:bda::4
12
ns2-34.azure-dns.net: 150.171.16.34
A
ns2-01.azure-dns.net (2620:1ec:8ec::1)
13
ns2-34.azure-dns.net: No AAAA record found
AAAA
ns2-01.azure-dns.net (2620:1ec:8ec::1)
14
ns3-34.azure-dns.org: 13.107.222.34
A
ns3-01.azure-dns.org (2a01:111:4000::1)
15
ns3-34.azure-dns.org: No AAAA record found
AAAA
ns3-01.azure-dns.org (2a01:111:4000::1)
16
ns4-34.azure-dns.info: 13.107.206.34
A
ns4-01.azure-dns.info (2620:1ec:bda::1)
17
ns4-34.azure-dns.info: No AAAA record found
AAAA
ns4-01.azure-dns.info (2620:1ec:bda::1)
18
ns1.bdm.microsoftonline.com: 40.90.4.208
A
ns1-34.azure-dns.com (150.171.10.34)
19
ns1.bdm.microsoftonline.com: 2603:1061::d0
AAAA
ns1-34.azure-dns.com (150.171.10.34)
20
ns2.bdm.microsoftonline.com: 64.4.48.208
A
ns1-34.azure-dns.com (150.171.10.34)
21
ns2.bdm.microsoftonline.com: 2620:1ec:8ec::d0
AAAA
ns1-34.azure-dns.com (150.171.10.34)
22
ns3.bdm.microsoftonline.com: 13.107.24.208
A
ns1-34.azure-dns.com (150.171.10.34)
23
ns3.bdm.microsoftonline.com: 2a01:111:4000::d0
AAAA
ns1-34.azure-dns.com (150.171.10.34)
24
ns4.bdm.microsoftonline.com: 13.107.160.208
A
ns1-34.azure-dns.com (150.171.10.34)
25
ns4.bdm.microsoftonline.com: 2620:1ec:bda::d0
AAAA
ns1-34.azure-dns.com (150.171.10.34)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
gset.co.th
0

no CAA entry found
1
0
co.th
0

no CAA entry found
1
0
th
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
gset.co.th
mscid=DfMDXd40UTX1fMLt1QnehgPnOy2MciKxxUQ3Ftoo+JDEnd35WgsyN+l1a3CmGU/KhJ5XB0p4e8d+Ms8JITzX/A==
ok
1
0
gset.co.th
v=spf1 include:spf.protection.outlook.com -all
ok
1
0
_acme-challenge.gset.co.th

Name Error - The domain name does not exist
1
0
_acme-challenge.gset.co.th.gset.co.th

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=1f83c006-cabe-483f-8880-bb31c59cbc8a


Last Result: https://check-your-website.server-daten.de/?q=gset.co.th - 2020-08-01 09:32:43


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

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