Hostname
theyardservice.com
Last fetched
theyardservice.com resolves to 178.162.202.96, announced in 178.162.192.0/18 by LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH in DE. theyardservice.com is listed by 3 threat feeds; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed by 3 threat feeds. At least one source recommends blocking.
Categories: Phishing
- Threat feeds listing this
- 3
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:51:23 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 00:24:18 GMT
Nutrition Label
Resolution chain
- 178.162.202.96
178.162.192.0/18 · LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH
- 178.162.202.97
178.162.192.0/18 · LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH
- 46.165.199.7
46.165.192.0/18 · LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH
- 46.165.199.9
46.165.192.0/18 · LEASEWEB-DE-FRA-10 - Leaseweb Deutschland GmbH
- 85.17.155.52
85.17.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 85.17.155.53
85.17.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 85.17.70.16
85.17.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 85.17.70.38
85.17.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V. · Amsterdam, NL
- 64.62.203.98
- 64.62.203.97
IPv6 resolution
Attribution
leaseweb deutschland
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- privacy service provided by withheld for privacy ehf
- Contact emails
- 90e6d3dccf3d4a6fb275c06b9e147b07.protect@withheldforprivacy.com, service@lains.com, reactivation-pending@mail.withheldforprivacy.com
Subdomains
Mail and authentication
Nameservers
- fake-for-negative-caching.adguard.com
- sinkhole-00.shadowserver.org
- sinkhole-01.shadowserver.org
- sinkhole-02.shadowserver.org
- sinkhole-03.shadowserver.org
- sinkhole-04.shadowserver.org
- sinkhole-a.shadowserver.org
- sinkhole-b.shadowserver.org
Threat-feed evidence
History
Related pages
Pivot from theyardservice.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: "theyardservice.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.