Hostname
lptedtech.com
Last fetched
lptedtech.com resolves to 13.227.192.118, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. lptedtech.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
- 13.227.192.118
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.13
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.24
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 13.227.192.70
13.227.192.0/24 · AMAZON-02 - Amazon.com, Inc. · Prague, CZ
- 18.245.60.12
18.245.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.60.62
18.245.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.60.72
18.245.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 18.245.60.87
18.245.60.0/22 · AMAZON-02 - Amazon.com, Inc. · Frankfurt am Main, DE
- 65.2.19.105
65.0.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Mumbai, IN
IPv6 resolution
No AAAA record for lptedtech.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:146
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns-103.awsdns-12.com
- ns17.domaincontrol.com
- ns18.domaincontrol.com
- ns-803.awsdns-36.net
- ns-1089.awsdns-08.org
- ns-1950.awsdns-51.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: dc-aa8e722993._spfm.lptedtech.com
Threat-feed evidence
History
Related pages
Pivot from lptedtech.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: "lptedtech.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.