Hostname
smartdigibook.com
Last fetched
smartdigibook.com resolves to 3.168.167.10, announced in 3.168.167.0/24 by AMAZON-02 - Amazon.com, Inc. in KR. smartdigibook.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
- 3.168.167.10
3.168.167.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.167.38
3.168.167.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.167.50
3.168.167.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.168.167.8
3.168.167.0/24 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 52.85.31.11
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.124
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.71
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 52.85.31.79
52.85.28.0/22 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 65.8.131.39
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.55
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.8
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.8.131.96
65.8.130.0/23 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
IPv6 resolution
No AAAA record for smartdigibook.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:625
- Registrant organisation
- domain protection services,
- Contact emails
- info@hakkanettevotjaks.ee
Subdomains
| Subdomain |
|---|
| reader.smartdigibook.com |
Showing 1 of 1 subdomain (1 per page).
Mail and authentication
Nameservers
- ns-377.awsdns-47.com
- ns-776.awsdns-33.net
- ns-1031.awsdns-00.org
- ns-1629.awsdns-11.co.uk
MX records
- smartdigibook-com.mail.protection.outlook.com
SPF policy
- include: amazonses.com
- include: spf.protection.outlook.com
Threat-feed evidence
History
Related pages
Pivot from smartdigibook.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: "smartdigibook.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.