Hostname
daklex.com
Last fetched
daklex.com resolves to 64.191.166.57, announced in 64.191.128.0/18 by ONERINGNET-ATL-1 - One Ring Networks, Inc. in US. daklex.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for daklex.com is recorded in WhisperGraph.
Attribution
one ring
ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- dermatology associates of kentucky
- Contact emails
- dd2ph5rp9mh@networksolutionsprivateregistration.com, kk62u3r5562@networksolutionsprivateregistration.com, licensing@daklex.com, prmiller@integrityky.com, qa8hz4sv7fq@networksolutionsprivateregistration.com, renewals@integrityky.com, tt56h7wv2z2@networksolutionsprivateregistration.com, uv2h22ns4va@networksolutionsprivateregistration.com, wu4648sz35k@networksolutionsprivateregistration.com, zy8jq4m76dm@networksolutionsprivateregistration.com
Subdomains
| Subdomain |
|---|
| autodiscover.daklex.com |
| citrix.daklex.com |
| connect.daklex.com |
| dev.daklex.com |
| owa.daklex.com |
| www.daklex.com |
Showing 6 of 6 subdomains (6 per page).
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns1-08.azure-dns.com
- ns4-08.azure-dns.info
- ns2-08.azure-dns.net
- ns3-08.azure-dns.org
MX records
- us-smtp-inbound-1.mimecast.com
- us-smtp-inbound-2.mimecast.com
SPF policy
- ip: 216.7.134.194/32
- a: daklex.com
- mx: daklex.com
- include: us._netblocks.mimecast.com
- include: spf.protection.outlook.com
- ip: 64.191.131.18
- ip: 64.191.131.19
- ip: 64.191.131.20
Threat-feed evidence
History
Related pages
Pivot from daklex.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "daklex.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.