Dataweaz

adspipe.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
December 15, 2000
Expires on
December 15, 2026
Name servers
udns1.cscdns.net, udns2.cscdns.uk
Mail servers
adspipe.in.tmes.trendmicro.com

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

DMARC tells mail servers what to do with an e-mail that claims to come from adspipe.com but fails SPF and DKIM checks.

Policy
Monitoring
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1; p=none; sp=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; fo=1; pct=100

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for adspipe.com.

RuleValueResult
mx—Allowed
ip463.64.60.202/32Allowed
ip4192.188.251.0/24Allowed
ip4199.167.63.33Allowed
ip4199.167.63.3Allowed
ip413.66.130.121/32Allowed
ip420.96.2.88/32Allowed
ip420.230.234.206/32Allowed
ip420.122.27.14/32Allowed
ip451.143.2.119/32Allowed
ip452.177.186.121/32Allowed
ip44.155.80.63/32Allowed
ip44.255.169.205/32Allowed
includespf.diligent.comAllowed
include_spf.q4press.comAllowed
include_spf.salesforce.comAllowed
includespf.tmes.trendmicro.comAllowed
includespf.protection.outlook.comAllowed
all—Rejected

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 mx ip4:63.64.60.202/32 ip4:192.188.251.0/24 ip4:199.167.63.33 ip4:199.167.63.3 ip4:13.66.130.121/32 ip4:20.96.2.88/32 ip4:20.230.234.206/32 ip4:20.122.27.14/32 ip4:51.143.2.119/32 ip4:52.177.186.121/32 ip4:4.155.80.63/32 ip4:4.255.169.205/32 include:spf.diligent.com include:_spf.q4press.com include:_spf.salesforce.com include:spf.tmes.trendmicro.com include:spf.protection.outlook.com -all

E-mail signing (DKIM)

DKIM keys published by adspipe.com under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 2048 bitsActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to adspipe.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from adspipe.com was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @adspipe.com address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

adspipe.com  MX  10 mx1.adspipe.com.
adspipe.com  MX  20 mx2.adspipe.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.adspipe.com.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

adspipe.com  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.adspipe.com, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.adspipe.com  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.adspipe.com, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.adspipe.com  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of adspipe.com

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A20.88.116.148

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
udns1.cscdns.net204.74.66.1
udns2.cscdns.uk204.74.111.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @adspipe.com addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
5adspipe.in.tmes.trendmicro.com18.208.22.78

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.adspipe.com.

NameContent
adspipe.comqbndt994djb339feqmpr1di4up
adspipe.comnkrq0pcvpeua6oigafucbjkv34
adspipe.comdknchofjvpcap93v001clve0om
adspipe.compardot855143=e01d1c24c25a7f5a8669315be492158f2ec6fb953f5b0ce841a8ce84d918d5aa
adspipe.com66occspnuepkv0b2pg0r38n0hf
adspipe.com7oijva13jnhorbq40f7jaf0o3k
adspipe.com7p07p0np6mp8j6nb2qbm8ie71q
adspipe.com7numtdk302gnma9k4dtrdma06d
adspipe.com6b1stjn92a9lg3vn01uihlplf6
adspipe.comgoogle-site-verification=XoTmTxtjyCgJpCdYQyHmA9C16dQbowF1ylzelINnbHA
adspipe.comlv1537q6vtub66cu2b5461vl2v
adspipe.comm398pb6j8ts701v5unjrh5bi2i
adspipe.com88tmume2eij7rbpllj8jacf730
adspipe.comblc9s202n34cgjpeb8flo04ni8
adspipe.comgeoqu12m6c3sb2ocsvcu02qtcu
adspipe.comadspipe.in.tmes.trendmicro.com.
adspipe.compaloaltonetworks-site-verification=979639516b02a6d8cbcd2bb339a2a30456d2e09487901925feca6a72b8b4f5e0
adspipe.comhhlbi2qhsqvtfgme5p2s741okq
adspipe.comapple-domain-verification=YCj1-VFpPf27gimn4hGiPdf_2QKdIXQCkRyLe7eJQLA
adspipe.com_8z4f3rpitdk9mxzh1v2w46mvgnor5uz
adspipe.com97vd1ev8chpjl800lfgsioovd6
adspipe.comwrike-verification=NTM0MTk2MzozMDE3ZGJjY2NjYmE4MDliMzRjYjg4MGU4YjNlMDQ1Mjk3MTI5MTYyM2ViNDJiNjhiYTIxMjE1YWMxYzhiNzkw
adspipe.comds1=b01be1d1-5096-4466-b2fe-0ef7b4758775
adspipe.comspvhphgb45l6ghb625mljzdslggcq7m8
adspipe.comhpe-greenlake-domain-verification=354f767157594a414d73734f4e70475965437359364b4d6b35506833494b4752
adspipe.comfigma-domain-verification=1cac3584fb39873665fc8400ba2901963bfe02f55d32388852a67ccf5fd72a8d-1742499888
adspipe.comk06nggh4ugiqveqoqo6k7rc87o
adspipe.com200608._domainkey.emails2.adspipe.com
adspipe.comsc1cerk0kkrpjcudfsk2pf4krk
adspipe.comul7dd0def43oghkrqtnsibup8j
adspipe.comdocusign=9a4f6ad4-d24f-48cf-a15d-9b7e069abd73
adspipe.comfacebook-domain-verification=k11lavkakea9ionqvh7w10sunfh5hx
adspipe.comg0giores48hbfk0a3ku2atnr3l
adspipe.comh5u1o0ohnkd8h1vedqh057ekcb
adspipe.comv=spf1 mx ip4:63.64.60.202/32 ip4:192.188.251.0/24 ip4:199.167.63.33 ip4:199.167.63.3 ip4:13.66.130.121/32 ip4:20.96.2.88/32 ip4:20.230.234.206/32 ip4:20.122.27.14/32 ip4:51.143.2.119/32 ip4:52.177.186.121/32 ip4:4.155.80.63/32 ip4:4.255.169.205/32 include:spf.diligent.com include:_spf.q4press.com include:_spf.salesforce.com include:spf.tmes.trendmicro.com include:spf.protection.outlook.com -all
adspipe.comchfl4pbji8nmsc7h18gh0s3i4a
adspipe.comrff85g0v61jm5jbd71578vnkv2
adspipe.com6fv7q7vmsie21rht1ri0ss6fog
adspipe.comteamviewer-sso-verification=7168e1eb07f74359b1a9900895e8e1e0
adspipe.com91ja9djj5veouvgv0gueqp4bda
adspipe.compardot855143=5999ce2bbd1a65eeb8fbd6aefc765aaae8828a229db5071b54456c3dbce39485
adspipe.comlb98mrul5eb5263itb7bs8gqjr
adspipe.com_dvm2cm8yz2orvsuhotouh0uzcavisqx
adspipe.comjnbbhlk0a2faei1i1qfig4j7od
adspipe.comt3sml75siljudsk28hfhhj0q6e
adspipe.comukvgk6kbfrhm2qhq5r11ugkp2l
adspipe.comtk13r0ifjl9bl9dioc8pa8qepa
adspipe.comjcilvs86mgneh35blsnpk4puqa
adspipe.com6qlz2wlgkhc7p55jsbzh3p2kwts4hp6k
adspipe.comctvjh9m1j5su3626d19kj3ats0
adspipe.com9fgndttld7s1kjtofr3192hls
adspipe.comremarkable-domain-verification=0b93ef01-c62f-4db8-b3c7-f102e36db6d5
adspipe.com9fddv4jcknbk1nao8to7ssbarh
adspipe.comm8r5bg5jla9ros0inacmh2dbrk
adspipe.com_pgxe3a92lqooc4ql9h3nlz3f4s98r8q
adspipe.com7l9lg4gp0fq946ma8s78eekjg2
adspipe.comt7s4tuvhi6o29u48997o8sbnfq
_dmarc.adspipe.comv=DMARC1; p=none; sp=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; adkim=r; aspf=r; fo=1; pct=100
selector1._domainkey.adspipe.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAq6On6EWxjLrB1ExHOu6E8wYrRppKyIy3uRgbMy/ata4XGcBQsxkHo5b8dApR7f0AM2iKXU/oYjRxZsN0sqbLCOFV0oJdqiwDLVoIqet0ROPvmuucn2HzAYTjX2m0AH0e81HDdHTlSMR0owl18DOIFr0PcWTMwc3ZsCpl9L3NDdF8h1opejE6Si4SeUH7VTV1TTRpKyJdPEF6qnvYFie7SU7XADmJjb+HTiH/DpIKaboI+GCWQ2lS0KFbOjjGv0/6MGcetFlb7v33B62/A6NZ3X98C9sKvMWwzT+cMkefIOLg9XKygdL6ef4z1ISuuXZsiaSr/jan+OsO6AOSPGj1FQIDAQAB;
s1._domainkey.adspipe.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA3rSt8T1z1w7cdjHYtbFooYwc9AxKhDZQzWfOl2007DIEkFPKVbC90IxY0ut3o/WBp95dP0LjXqE2EZwu/Htmx0a6hBO5GTA4aKtXlkiZTr9cD9lJAbVAZQbgh09bk2c9PJKkx9hbDq/lr4ECqP1Vh0PgAStyH88I0tILHzYuhU1Xs/wZ9PS4AP5AexDeDcmAP5ipUT66KuAktE0SMIAfj4PqjpQrT951gH80vtrgwpaQ1It8hkVpus8EZaWCcMglTOP7gKlI091c64K+GAJOqZ9VL+rjrskSzUXH2sRONLzuGlImfHKF+59WLwrdcE9bCXJdweIzqBsu5tnR3NGgwwIDAQAB
s2._domainkey.adspipe.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyoy5Pe98+O2TZt+Rzs3KydfXu6rTEyrqBdHzYzA7Xu6065fGslLAWogNJu7tTOlEycDN3imhNjCPahk8ITJECIqfutXKzcvC9frMRyGg2V02oBOiVWcI3GV6m6/f0o9dSIC2ks9hcURy9CEBUAPsGuBbRcmPc4T0RUEGBiTV9gKVIbPVf4O6LLqYAjLTMu7JeLWx4bD+GNNFUZNy3er00T5kMPWjBu5UFf9kBw+oAavCle4VAb0WqE+wWI1es9pD1i/0dVlv6n7/ZHE8o3qtrmxnjkQHvhzof2B+U5vRNRnBPT96O6opigTv5Bt+VfmK9UWG8sEekgdYKPB/0Q4ObwIDAQAB

Related IP addresses

IPv4 addresses used by adspipe.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
20.88.116.148Website20.88.116.0/24
204.74.66.1Name server udns1.cscdns.net204.74.66.0/24
204.74.111.1Name server udns2.cscdns.uk204.74.111.0/24
18.208.22.78Mail server adspipe.in.tmes.trendmicro.com18.208.22.0/24
63.64.60.202Authorized by SPF63.64.60.0/24
199.167.63.33Authorized by SPF199.167.63.0/24
199.167.63.3Authorized by SPF199.167.63.0/24
13.66.130.121Authorized by SPF13.66.130.0/24
20.96.2.88Authorized by SPF20.96.2.0/24
20.230.234.206Authorized by SPF20.230.234.0/24
20.122.27.14Authorized by SPF20.122.27.0/24
51.143.2.119Authorized by SPF51.143.2.0/24
52.177.186.121Authorized by SPF52.177.186.0/24
4.155.80.63Authorized by SPF4.155.80.0/24
4.255.169.205Authorized by SPF4.255.169.0/24

WHOIS of the domain adspipe.com

Domain Name: ADSPIPE.COM
   Registry Domain ID: 48640688_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2025-12-11T06:04:21Z
   Creation Date: 2000-12-15T14:29:58Z
   Registry Expiry Date: 2026-12-15T14:29:58Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: UDNS1.CSCDNS.NET
   Name Server: UDNS2.CSCDNS.UK
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T20:15:58Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.