DNS report
flo-bio.com
Complete DNS, mail, web and security analysis.
DNS cache tools
If you have recently made DNS changes and they are not yet reflected in the report, you can try to flush the DNS cache of these public resolvers: The domain name will be copied to your clipboard automatically when clicking on a button
| Category | Status | Test | Details | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
WHOIS0.2 ms |
Domain Status |
Source: WHOIS (port 43) grs-whois.hichina.com
Registrar lock not detected Warning: no public transfer lock status was found. Confirm with the registrar that transfer lock is enabled to reduce the risk of unauthorized transfer. |
|||||||||||||||||||||||||
| Warning | Delegated nameservers are not responding |
The domain flo-bio.com is delegated at the parent, but DNSprobe could not get a response from the delegated nameservers. The nameserver IPs may be offline, filtered, or no longer assigned, so the DNS zone cannot currently be reached.
Delegated nameservers with no response: dns17.hichina.com [47.118.199.220] dns18.hichina.com [47.118.199.222] |
|||||||||||||||||||||||||
|
PARENT0.0 ms |
Domain NS records |
Nameserver records returned by the parent servers are:
dns17.hichina.com [47.118.199.220] (GLUE) [TTL=172800] dns18.hichina.com [47.118.199.222] (GLUE) [TTL=172800] c.gtld-servers.net was kind enough to give us that information. |
|||||||||||||||||||||||||
| TLD Parent Check |
c.gtld-servers.net has information for your TLD.
This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check. |
||||||||||||||||||||||||||
| Your nameservers are listed |
c.gtld-servers.net has your nameservers listed.
This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. |
||||||||||||||||||||||||||
| DNS Parent sent Glue |
2 of 2 nameservers sent GLUE.
The parent nameserver a.gtld-servers.net sent GLUE, meaning it sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver. (See RFC 1912 section 2.3) |
||||||||||||||||||||||||||
| Nameservers A records |
Every nameserver listed has A records.
This is a must if you want to be found. |
||||||||||||||||||||||||||
|
NS0.2 ms |
NS records from your NameServers |
NS records returned by the currently delegated nameservers are:
Oops! I could not get any nameservers from your nameservers. Please verify that the nameservers listed at the parent are not lame and are configured properly. Nameservers with no NS response: dns17.hichina.com dns18.hichina.com |
|||||||||||||||||||||||||
| Public Resolver |
|
||||||||||||||||||||||||||
| Mismatched NS records |
Comparison skipped: the authoritative nameservers did not return NS records, so DNSprobe is using the parent delegation only to continue the diagnosis.
|
||||||||||||||||||||||||||
| DNS servers responded |
The following NS did not respond to a basic query:
dns17.hichina.com dns18.hichina.com ❌ These nameservers did not respond to a standard non-recursive A query. This may indicate filtering, timeouts, or misconfiguration. |
||||||||||||||||||||||||||
| DNS zone may not be configured |
The domain is delegated at the parent, but the delegated nameservers did not return NS records for this domain. This usually means the DNS zone is missing, not loaded, or not configured correctly on the authoritative servers.
|
||||||||||||||||||||||||||
| Name of nameservers are valid |
All of the NS records that your nameservers report seem valid.
|
||||||||||||||||||||||||||
| Multiple Nameservers |
You have 2 nameservers. This is acceptable, but having 3 or more is recommended according to RFC2182 section 5.
Having 2 nameservers is ok by me. |
||||||||||||||||||||||||||
| Missing nameservers reported by parent |
All NS records are the same at the parent and at your nameservers.
|
||||||||||||||||||||||||||
| Missing nameservers reported by your nameservers |
Test skipped: no authoritative nameserver returned NS records, so DNSprobe cannot verify whether the child zone contains all nameservers listed at the parent.
|
||||||||||||||||||||||||||
| Domain CNAMEs |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||
| NSs CNAME check |
OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present.
|
||||||||||||||||||||||||||
| Different subnets |
All nameservers are on the same subnet (can be a risk).
|
||||||||||||||||||||||||||
| Recursive Queries |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| Same Glue |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| NS Self-IP Consistency |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| Glue for NS records |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| Nameservers are lame |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| IPs of nameservers are public |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| DNS servers allow TCP connection |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| Different autonomous systems |
Test skipped because no authoritative nameserver responded well enough to perform this check.
|
||||||||||||||||||||||||||
| Stealth NS records sent |
Ok. No stealth NS records are sent
|
||||||||||||||||||||||||||
|
MX ... |
MX Records |
|
|||||||||||||||||||||||||
|
DKIM ... |
DKIM Records Detected |
|
|||||||||||||||||||||||||
|
SSL ... |
SSL Certificate Summary |
|
|||||||||||||||||||||||||
|
CAA ... |
CAA Records |
|
|||||||||||||||||||||||||
|
HSTS ... |
HSTS |
|
|||||||||||||||||||||||||
|
HTTPS ... |
HTTPS |
|
|||||||||||||||||||||||||
|
HTTPS (DNS) ... |
HTTPS DNS record |
|
|||||||||||||||||||||||||
|
WWW ... |
A Record |
|
|||||||||||||||||||||||||
|
DNS found ... |
|
||||||||||||||||||||||||||
| Test | Details | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
WHOIS101.2 ms
|
Source: WHOIS (port 43) grs-whois.hichina.com
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
RDAP 100.9 ms
|
Source: RDAP rdap.org → rdap.verisign.com → whois.aliyun.com
Registrar
RDAP JSON (raw){
"objectClassName": "domain",
"handle": "3127880641_DOMAIN_COM-VRSN",
"ldhName": "FLO-BIO.COM",
"links": [
{
"value": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"rel": "self",
"href": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"type": "application/rdap+json"
},
{
"value": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"rel": "related",
"href": "https://whois.aliyun.com/rdap/domain/FLO-BIO.COM",
"type": "application/rdap+json"
}
],
"status": [
"active"
],
"entities": [
{
"objectClassName": "entity",
"handle": "1599",
"roles": [
"registrar"
],
"links": [
{
"href": "http://wanwang.aliyun.com",
"type": "text/html",
"value": "https://whois.aliyun.com/rdap/",
"rel": "about"
}
],
"publicIds": [
{
"type": "IANA Registrar ID",
"identifier": "1599"
}
],
"vcardArray": [
"vcard",
[
[
"version",
[],
"text",
"4.0"
],
[
"fn",
[],
"text",
"Alibaba Cloud Computing Ltd. d/b/a HiChina (www.net.cn)"
]
]
],
"entities": [
{
"objectClassName": "entity",
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
[],
"text",
"4.0"
],
[
"fn",
[],
"text",
""
],
[
"tel",
{
"type": "voice"
},
"uri",
"tel:+86.95187"
],
[
"email",
[],
"text",
"[email protected]"
]
]
]
}
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2026-08-02T09:42:49Z"
},
{
"eventAction": "expiration",
"eventDate": "2027-08-02T09:42:49Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-08-02T10:45:11Z"
},
{
"eventAction": "last update of RDAP database",
"eventDate": "2026-09-20T10:35:58Z"
}
],
"secureDNS": {
"delegationSigned": false
},
"nameservers": [
{
"objectClassName": "nameserver",
"ldhName": "DNS17.HICHINA.COM"
},
{
"objectClassName": "nameserver",
"ldhName": "DNS18.HICHINA.COM"
}
],
"rdapConformance": [
"rdap_level_0",
"icann_rdap_technical_implementation_guide_1",
"icann_rdap_response_profile_1"
],
"notices": [
{
"title": "Terms of Service",
"description": [
"Service subject to Terms of Use."
],
"links": [
{
"href": "https://www.verisign.com/domain-names/registration-data-access-protocol/terms-service/index.xhtml",
"type": "text/html",
"value": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"rel": "terms-of-service"
}
]
},
{
"title": "Status Codes",
"description": [
"For more information on domain status codes, please visit https://icann.org/epp"
],
"links": [
{
"href": "https://icann.org/epp",
"type": "text/html",
"value": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"rel": "glossary"
}
]
},
{
"title": "RDDS Inaccuracy Complaint Form",
"description": [
"URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf"
],
"links": [
{
"href": "https://icann.org/wicf",
"type": "text/html",
"value": "https://rdap.verisign.com/com/v1/domain/flo-bio.com",
"rel": "help"
}
]
}
]
} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
You like this tool?
Processed in 0.004 seconds.
Made with with PHP and a bit of JS.
Made with with PHP and a bit of JS.
Lines of code: 20,351
