Hostname
demys.com
Last fetched
demys.com resolves to 100.28.104.175, announced in 100.24.0.0/13 by AMAZON-AES - Amazon.com, Inc. in US. demys.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
- 100.28.104.175
100.24.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.185.24.46
18.184.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.126.5.188
3.124.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 3.71.139.153
3.64.0.0/12 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 54.157.108.158
54.156.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.83.184.133
98.80.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:470
- Registrant organisation
- domain admin.
- Contact emails
- demys.com+registrant@customer.demys.com, gtld@demys.com, demys.com-registrant@anonymised.email
Subdomains
| Subdomain |
|---|
| fwtestdomain.demys.com |
| fwtestdomain2.demys.com |
| manage.demys.com |
| newgtld.demys.com |
| parked.demys.com |
| spf.demys.com |
| whois.demys.com |
| www.demys.com |
Showing 8 of 8 subdomains (8 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
- ns0.demysdns.net
- ns1.demysdns.net
- ns2.demysdns.net
- ns3.demysdns.net
- ns4.demysdns.co.uk
- ns5.demysdns.co.uk
- ns6.demysdns.co.uk
MX records
- demys-com.mail.protection.outlook.com
SPF policy
- ip: 87.246.68.0/24
- include: emailsrvr.com
- include: spf.protection.outlook.com
- include: servers.mcsv.net
- ip: 198.143.161.28
- ip: 77.104.149.148
- ip: 84.19.241.194
- ip: 92.234.12.67
Threat-feed evidence
History
Related pages
Pivot from demys.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: "demys.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.