Analysis report on domain: spamcop.net favicon

spamcop.net
Generated on
03 Jul 2018 11:16
Duration of the analysis
28.5s
Share

Score 74%
E
DNS
A
DOMAIN
A
MAIL
E
WEB
A

Resume

SMTP server number

There is only one valid SMTP server.

DMARC procedure exists

The field "p" is missing in "{1}"

STARTTLS command is accepted

vmx5.spamcop.net [184.94.240.124] does not accept TLS.

VRFY command is refused

vmx5.spamcop.net [184.94.240.124] authorizes VRFY command.

MX servers accept abuse@ address

vmx5.spamcop.net [184.94.240.124] does not accept email to abuse@spamcop.net.

MX servers accept postmaster@ address

vmx5.spamcop.net [184.94.240.124] does not accept email to postmaster@spamcop.net.

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

Content Security Policy header is present

The Content-Security-Policy header was not found.

DKIM is configured for domain

We do not detect any DKIM record for this domain.

DNS

Dns servers for spamcop.net

spamcop.net was detected as domain

Query informations

Server
a.root-servers.net
[ 198.41.0.4 ]
Duration
16 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
a.gtld-servers.net
[ 192.5.6.30 ]
Duration
926 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
b.gtld-servers.net
[ 192.33.14.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
c.gtld-servers.net
[ 192.26.92.30 ]
Duration
26 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
d.gtld-servers.net
[ 192.31.80.30 ]
Duration
26 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
e.gtld-servers.net
[ 192.12.94.30 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
f.gtld-servers.net
[ 192.35.51.30 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
g.gtld-servers.net
[ 192.42.93.30 ]
Duration
35 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
h.gtld-servers.net
[ 192.54.112.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
i.gtld-servers.net
[ 192.43.172.30 ]
Duration
29 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
j.gtld-servers.net
[ 192.48.79.30 ]
Duration
28 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
k.gtld-servers.net
[ 192.52.178.30 ]
Duration
131 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
l.gtld-servers.net
[ 192.41.162.30 ]
Duration
132 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
m.gtld-servers.net
[ 192.55.83.30 ]
Duration
133 ms
Type
authority
Headers
RCODE : 0AA : 0TC : 0

Response

Query informations

Server
asia3.akam.net
[ 23.211.61.64 ]
Duration
6 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-109.akam.net
[ 193.108.91.109 ]
Duration
41 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-11.akam.net
[ 193.108.91.11 ]
Duration
28 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-117.akam.net
[ 193.108.91.117 ]
Duration
43 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-73.akam.net
[ 193.108.91.73 ]
Duration
25 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-90.akam.net
[ 193.108.91.90 ]
Duration
31 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
ns1-93.akam.net
[ 193.108.91.93 ]
Duration
42 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Query informations

Server
use1.akam.net
[ 72.246.46.64 ]
Duration
161 ms
Type
answer
Headers
RCODE : 0AA : 1TC : 0

Response

Name servers

Mx Servers

Name
vmx5.spamcop.net
IPs
Priority
5
TTL
300 (5 minutes)

A and AAAA fields

IPv4
95.100.252.24
TTL
20 (20 seconds)
IPv4
95.100.252.10
TTL
20 (20 seconds)

Text Fields

Type
Spf (TXT)
TTL
300 (5 minutes)
Name
@
Raw data
v=spf1 ip4:184.94.240.89 ip4:184.94.240.112 ip4:68.232.142.20 ip4:68.232.143.151 ~all
IPv4
ALL
~all
Type
Dmarc
TTL
300 (5 minutes)
Raw data
v=DMARC1 p=none sp=reject aspf=r ruf=mailto:dmark@spamcop.net rua=mailto:dmark@spamcop.net
Version
DMARC1 p=none sp=reject aspf=r ruf=mailto:dmark@spamcop.net rua=mailto:dmark@spamcop.net

SOA

From
use1.akam.net
Master server
ns1-93.akam.net
TTL
300 (5 minutes)
Contact
fIOHiIF1h4h5hg==@akamai.com
Serial
1519312683
Refresh
300 (5 minutes)
Retry
300 (5 minutes)
Expire
300 (5 minutes)
Minimum
300 (5 minutes)

Hosts found

Name
www.spamcop.net
Cname
spamcop.net.edgekey.net
TTL
300 (5 minutes)
Name
smtp.spamcop.net
Cname
vmx5.spamcop.net
TTL
300 (5 minutes)
Name
mx.spamcop.net
IP
64.88.168.82
IP
64.88.168.74
TTL
300 (5 minutes)
Name
imap.spamcop.net
Cname
vmx5.spamcop.net
TTL
300 (5 minutes)
Name
pop.spamcop.net
IP
216.154.195.50
TTL
300 (5 minutes)

BIND version is hidden

Passed

The Bind version should not be visible otherwise it will be possible to search for potential security vulnerabilities of the version.

0.277s

Domain have at least 2 DNS servers

Passed

In order for the availability rate of DNS servers to be at its highest, it is vital and recommended by the RFC to have at least 2 servers.

RFC

0.000s

All Dns servers are responding

Passed

Every DNS servers should be accessible and accept public query.

0.009s

All servers return success

Passed

It's important that all servers returned a "success" code.

0.008s

Responses are not CNAME or A

Passed

The answers should not be a CNAME or A type.

RFC

0.008s

DNS servers IP are differents

Passed

IPs for DNS servers must be different in order to have high availability.

0.000s

DNS servers IP are in different class C

Passed

The class C of each IP must be different so that the servers are not found on the same bay and therefore there is a risk of unavailability.

RFC

0.001s

DNS servers are synchronized

Passed

The synchronization of the DNS servers must be perfect in order to avoid any dns resolution error. The servers must therefore give the same answer when asked "what are the DNS servers for the domain?".

0.001s

SOA are synchronized

Passed

The SOA answered by the DNS servers must be identical for each servers. The most important information is the master server and the contact email address.

0.000s

SOA email is valid

Passed

An email address must respect some conditions to be valid, accordding to the RFC 5322.

RFC

0.000s

SOA refresh is valid

Passed

The refresh value be must between 1200 and 43200.

RFC

0.000s

SOA retry, refresh and expire values are correct

Passed

The Retry, Refresh and Expire values musth follow this path : retry < refresh < expire.

RFC

0.000s

DNS servers are not open relay

Passed

DNS resolvers that allow queries from all IP addresses and are exposed to the Internet can be attacked and used to conduct Denial of Service (DoS) attacks on behalf of the hacker.

0.277s

Transfer zone is disable

Passed

An attacker can use a zone transfer that contains a malicious code or an inappropriate format that crashes a DNS server vulnerable to this type of attack, which results in a DoS that destabilizes the DNS services. It is possible to test it manually with this commands: #host -T axfr or #dig axfr.

documentation

0.736s

Recursive query is disable

Passed

Having a dns server that allow recursive queries is a security risk, DDOS attack can be performed.

RFC documentation documentation

0.277s

DNS servers IP are not private

Passed

It is strictly forbidden to have private IP in DNS

documentation

0.000s

Same MX are returned

Passed

It is extremely important that each DNS return the same MX records in order to avoid contacting an SMTP server that no longer exists.

0.287s

Domain

Whois

Registrar
eNom, Inc.
Owner
-
Created at
30 Jan 1999
Changed at
01 Jan 2018
Expires at
30 Jan 2019

Reputation

Google Safe Browsing
Web of trust
94%
Blacklists
Virus Total
Domain
Registrar
Id
48
Name
eNom, Inc.
Phone
-
Email
Url
-

Google Safe Browsing

Status

Web of Trust

Trust Rate
94%
Child Safe Rate
95%
Categories
Good site

Blacklists

RFC Ignorant
Rbl Jp
RblDns
Sorbs
Spam Eating Monkey
SpamHaus
SuRbl
Support Intelligence
Swinog
UriBl

Virus Total

Detection ratio
0 / 67

Scans

ADMINUSLabs
AegisLab WebGuard
AlienVault
Antiy-AVL
Avira
Baidu-International
BitDefender
Blueliv
C-SIRT
CLEAN MX
Certly
Comodo Site Inspector
CyRadar
CyberCrime
DNS8
Dr.Web
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
FraudScore
FraudSense
G-Data
Google Safebrowsing
K7AntiVirus
Kaspersky
Malc0de Database
Malekal
Malware Domain Blocklist
MalwareDomainList
MalwarePatrol
Malwarebytes hpHosts
Malwared
Nucleon
OpenPhish
Opera
Phishtank
Quttera
Rising
SCUMWARE.org
SecureBrain
Spam404
Sucuri SiteCheck
Tencent
ThreatHive
Trustwave
VX Vault
Virusdie External Site Scan
Web Security Guard
Webutation
Yandex Safebrowsing
ZCloudsec
ZDB Zeus
ZeroCERT
Zerofox
ZeusTracker
desenmascara.me
malwares.com URL checker
securolytics
zvelo
AutoShun
Netcraft
NotMining
PhishLabs
Sophos
StopBadware
URLQuery

DNS servers are same in dns tree and whois

Passed

The dns servers given in the domain whois must be the same as those returned by a dns resolution request.

0.000s

Domain is not blacklisted

Passed

A domain must not be blacklisted or it will be penalized for referencing and deliverability of emails.

0.000s

Domain is not listed in Google Safe Browsing

Passed

Google safe browsing categorizes a domain as bad if something suspicious is detected.

0.000s

Domain is not listed in VirusTotal

Passed

Virus Total analyze your domain or IP address with 66 antivirus.

0.000s

Domain have good reputation on Web of Trust

Passed

Web Of Trust rates thousands of websites and find threats if they exist.

0.000s

Mail

Mail servers

Name
vmx5.spamcop.net
IP
184.94.240.124
Banner
220 vmx5.spamcop.net ESMTP

SPF

Find more informations about this SPF entry into the DNS> Zone tab

Raw data
v=spf1 ip4:184.94.240.89 ip4:184.94.240.112 ip4:68.232.142.20 ip4:68.232.143.151 ~all

DMARC

Find more informations about this DMARC entry into the DNS> Zone tab

Raw data
v=DMARC1 p=none sp=reject aspf=r ruf=mailto:dmark@spamcop.net rua=mailto:dmark@spamcop.net
Name
vmx5.spamcop.net
IP
184.94.240.124
Banner
220 vmx5.spamcop.net ESMTP
Starttls
no
Mail size
9.77 MB
Expn
no
Vrfy
yes

Smtp simulation

Connection to vmx5.spamcop.net ...
220 vmx5.spamcop.net ESMTP
HELO nstools.fr
250 vmx5.spamcop.net
EHLO nstools.fr
250-vmx5.spamcop.net
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
QUIT
221 2.0.0 Bye

SMTP server number

There is only one valid SMTP server.

Domain should have at least 2 SMTP servers according to the RFC

0.000s

DMARC procedure exists

The field "p" is missing in "{1}"

According to the RFC 7489 section 6.3, the procedure is required.

RFC

0.000s

STARTTLS command is accepted

vmx5.spamcop.net [184.94.240.124] does not accept TLS.

STARTTLS turns an unencrypted connection into a secure connection.

0.000s

VRFY command is refused

vmx5.spamcop.net [184.94.240.124] authorizes VRFY command.

As the EXPN command, VRFY is used by spammers to verify an address.

0.000s

MX servers accept abuse@ address

vmx5.spamcop.net [184.94.240.124] does not accept email to abuse@spamcop.net.

According to the RFC 2142, SMTP server should accept abuse@yourDomain as a recipient.

RFC

1.241s

MX servers accept postmaster@ address

vmx5.spamcop.net [184.94.240.124] does not accept email to postmaster@spamcop.net.

According to the RFC 5321, SMTP server should accept postmaster@yourDomain as a recipient.

RFC

1.117s

DKIM is configured for domain

We do not detect any DKIM record for this domain.

It is strongly recommended to configure DKIM.

0.000s

MX servers are accessibles

Passed

Smtp servers that are listed in DNS area must be accessible, otherwise, there is a risk that emails may be lost

0.000s

MX IPs have reverse

Passed

When a sending server makes a connection to the recipient server, the recipient server notes the sending IP address and performs a reverse lookup, called a PTR lookup, named after the type of DNS record used. If the result of the reverse lookup matches the result of a forward DNS Lookup, then it's much more likely that the message is legitimate. If the IP address doesn't match, it's much more likely that the sending address was spoofed and therefore much more likely that it's unwanted and could be considered spam.

documentation

0.000s

HELO command is accepted

Passed

According to the RFC 2181, smtp server should accept HELO command

RFC

0.000s

EHLO command is accepted

Passed

According to the RFC 2181, smtp server should accept EHLO command

RFC

0.000s

EXPN command is refused

Passed

EXPN command is now considered to be a security risk, spammers being able to harvest valid e-mail addresses via each mailing list.

0.000s

MX servers are not open relay

Passed

If a server is open relay, there is a risk that spammers use your server to send illegitimate mail.

3.042s

Banner return 2xx or 4xx code

Passed

The banner must return (2xx) a valid (4xx) or temporary code.

0.000s

Banner return server name

Passed

Banner must contain the name of the server

0.000s

SMTP server type is hidden

Passed

There is a risk to display the type and the version of the server, because people can find a breach for a specific version and use it

0.000s

MX records are FQDN

Passed

MX must be a domain, not an IP.

RFC

0.000s

MX records are not CNAME

Passed

According to the RFC 1034 and 2181 CNAME records should not be used with NS and MX

RFC RFC

0.021s

SPF is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure SPF.

0.000s

SPF record is TXT type

Passed

SPF record is no longer used, SPF must be into TXT record because many servers do not support SPF record. If SPF record exist, it should be the same as TXT

RFC

0.000s

Domain have only 1 SPF record

Passed

To avoid issue with SPF, it is strongly recommended to configure only one.

0.000s

SPF version exists

Passed

According to the RFC, the SPF version must be specified.

RFC

0.000s

SPF version at first position

Passed

SPF has to start with version's tag.

RFC

0.000s

SPF "all" exists

Passed

According to the RFC, the mecanism "all" must be specified in the SPF record, except if there is a Redirect tag.

RFC

0.000s

SPF "all" at last position

Passed

The mecanism "All" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

IPv4 & IPv6 syntaxes are corrects in SPF

Passed

IPs must be valid, otherwise the SPF will be useless.

RFC

0.000s

SPF haven't PTR

Passed

PTR has become obselete in SPF, should not be found in it.

RFC

0.000s

SPF "Redirect" at last position

Passed

The mecanism "Redirect" has to be the last tag in SPF record. Be sure you don't have any dupplicates entry in your field.

RFC

0.000s

SPF records of type TXT & SPF are the same

Passed

SPF record has become obselete, if it is configured then it must be the same as the one present in the TXT record

0.000s

DMARC is configured for domain

Passed

To avoid identity theft, it is strongly recommended to configure DMARC.

0.000s

Domain have only 1 DMARC record

Passed

To avoid issue with DMARC, it is strongly recommended to configure only one.

0.000s

DMARC version exist

Passed

According to the RFC 7489 section 6.3, the DMARC version is required.

RFC

0.000s

DMARC version at first position

Passed

According to the RFC 7489 section 6.3, the DMARC version must be the first tag in the list.

RFC

0.000s

DMARC "p" field is valid

Passed

According to the RFC 7489 section 6.3, the procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "sp" field is valid

Passed

According to the RFC 7489 section 6.3, the subdomain procedure value must be none, quarantine or reject.

RFC

0.000s

DMARC "pct" field is valid

Passed

According to the RFC 7489 section 6.3, the percentage's value must be between 0 and 100.

RFC

0.000s

DMARC "adkim" field is valid

Passed

According to the RFC 7489 section 6.3, the adkim tag value must be the letter R or S.

RFC

0.000s

DMARC "aspf" field is valid

Passed

According to the RFC 7489 section 6.3, the aspf tag value must be the letter R or S.

RFC

0.000s

DMARC "rf" field is valid

Passed

According to the RFC 7489 section 6.3, the RF tag's value must be afrf or iodef.

RFC

0.000s

DMARC "ri" field is valid

Passed

According to the RFC 7489 section 6.3, the RI tag's value must be an integer.

RFC

0.000s

DMARC "ruf" field is valid

Passed

According to the RFC 7489 section 6.3, the RUF tag's value must be a valid email.

RFC

0.000s

DMARC "rua" field is valid

Passed

According to the RFC 7489 section 6.3, the RUA tag's value must be a valid email.

RFC

0.000s

MX IPs are differents

Skipped

The IP of the SMTP servers must be different if it is no longer reachable.

0.000s

MX IPs are in different class C

Skipped

The class C of every IPs should be differents

0.000s

DKIM version exist

Skipped

According to the RFC 6376 section 3.6.1, the DKIM version is required.

RFC

0.000s

DKIM Service Type is valid

Skipped

This Tag is optionnal but when use, it must be equal to "*" or "email".

RFC

0.000s

DKIM Testing flag is valid

Skipped

This Tag is optionnal but when use, it must be equal to "s", "y" or "y:s".

RFC

0.000s

DKIM public key is valid

Skipped

According to the RFC 6376 section 3.6.1, the public key is required and must be valid.

RFC

0.000s

DKIM public key is secure

Skipped

The size of the public key must be bigger than 1024 bits.

0.000s

Web

Website

Url
https://www.spamcop.net/
Https
Title
SpamCop.net - Beware of cheap imitations
Description
Beware of cheap imitations! SpamCop has been protecting the internet community since 1998. Automatically file spam reports with the network administrators who can stop unsolicited email at the source. Subscribe, and filter your email before it reaches your inbox.
First paragraph
Report spam to help Internet providers cut spam off at the source. Register Now Find out about SpamCop reports and spam blocking, email deliverability problems and what you can do to ensure that your mail will get through. Learn More Get information from SpamCop's extensive FAQ and active user community. Help Home
Url
http://www.spamcop.net/
Redirect to
https://www.spamcop.net/
Redirect code
301 - moved permanently

Headers

  • Cache-Control: max-age=0, no-cache, no-store
  • Connection: close
  • Content-Length: 232
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Tue, 03 Jul 2018 11:16:46 GMT
  • Expires: Tue, 03 Jul 2018 11:16:46 GMT
  • Location: https://www.spamcop.net/
  • Pragma: no-cache
  • Server: Apache
Url
https://www.spamcop.net/
Title
SpamCop.net - Beware of cheap imitations
Description
Beware of cheap imitations! SpamCop has been protecting the internet community since 1998. Automatically file spam reports with the network administrators who can stop unsolicited email at the source. Subscribe, and filter your email before it reaches your inbox.
Response time
0.849 second
Server
apache
Powered by
Unknown
Encoding
iso-8859-1
HSTS

Headers

  • Accept-Ranges: bytes
  • Cache-Control: max-age=0, no-cache, no-store
  • Connection: close
  • Content-Length: 5190
  • Content-Type: text/html; charset=iso-8859-1
  • Date: Tue, 03 Jul 2018 11:16:47 GMT
  • Expires: Tue, 03 Jul 2018 11:16:47 GMT
  • Pragma: no-cache
  • Server: Apache
  • Strict-Transport-Security: max-age=31536000; includeSubDomains
  • X-Content-Security-Policy: allow 'self';
  • X-Content-Type-Options: nosniff
  • X-Frame-Options: DENY
  • X-Permitted-Cross-Domain-Policies: none
  • X-XSS-Protection: 1; mode=block

Domain have "AAAA" field

Host has no "AAAA" (IPv6) field.

It is highly recommended to have an IPv6 for the website.

0.000s

Content Security Policy header is present

The Content-Security-Policy header was not found.

The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (XSS).

documentation

0.000s

Domain have "A" field

Passed

The domain must have an A field in order for the website to be accessible.

0.000s

Host "www" have "A" field

Passed

WWW host is not required for a website, but it's better to have one.

0.000s

Host "www" have "AAAA" field

Passed

If you configure a WWW host for your website, it is recommended to have an IPv6.

0.000s

HTTP port (80) is open

Passed

This test verifies the presence of a website for the given IP or domain. Then scans port 80.
If the domain or IP is pointing to a website then port 80 must be open so that it can be accessed from a browser.
Otherwise port 80 must be closed.

0.000s

HTTPS port (443) is open

Passed

This test verifies the presence of a website for the given IP or domain. Then scans port 443.
If the domain or IP is pointing to a website then port 443 must be open so that it can be accessed from a browser.
Otherwise port 443 must be closed.

0.000s

Web server version is hidden

Passed

To avoid giving details to malicious people, the version of the server should not be visible.

0.000s

Web application technology is hidden

Passed

To avoid giving details to malicious people, the technology that supports the application should not be visible.

0.000s

X-XSS-Protection header is present

Passed

The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.

documentation

0.000s

Content Type Options header is present

Passed

The only defined value, "nosniff", prevents Internet Explorer from MIME-sniffing a response away from the declared content-type. This also applies to Google Chrome, when downloading extensions.

0.000s

Cookies are secure

Skipped

Using "HttpOnly" instruction prevents someone to access to cookies via Javascript. The secure flag will allow you to prevent a cookie from ever being communicated in simple HTTP. (RFC 6265 section 8.3)

RFC

0.000s